-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"TypeError: URLBrowserResolver is not a constructor" error in nodejs since V0.1.66 #2037
Labels
Comments
As a (very) dirty hack, to get things working in node (when calling getBuffer() etc) I have temporarily hacked a few lines of code into the built
|
liborm85
added a commit
that referenced
this issue
Jul 30, 2020
|
I have tested this on a local copy. Seems to do the trick. |
New version released. |
moshensky
pushed a commit
to moshensky/pdfmake
that referenced
this issue
Nov 16, 2020
* 0.1: (60 commits) fix auto page height for table bpampuch#2005 0.1.68 update dependencies fixed check window exists bpampuch#2037 0.1.67 refresh pdf examples fix for overrides window.Promise EP bpampuch#2026 reformat bug-2021-bad-svg-parsing * switch to using xmldoc backport to 0.1: loading images via URL in browser bug-2021-bad-svg-parsing * fix for writeDimensions() bug-2021-bad-svg-parsing * failing test for writeDimensions() bug-2021-bad-svg-parsing * fix to ignore comments when identifying <svg> tag bug-2021-bad-svg-parsing * add failing tests 0.1.66 fonts available in cdn backport to 0.1: support for loading raw font files by url address via http(s) protocol for browser usage define node version in package.json fix for babel bpampuch#1846 travis - run first on linux ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, prior to v0.1.66, calls to
getBuffer()
andgetBase64()
worked perfectly well in NODE (v12) but since the addition of URLBrowserResolver.js in V0.1.66 the following code fails...First run, this error occurs...
subsequent runs, this error occurs...
The text was updated successfully, but these errors were encountered: