-
Notifications
You must be signed in to change notification settings - Fork 1.2k
'document is not defined' in units-css/lib/utilities.js #898
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
Comments
Wow that's not good, there should be no references to |
I'm rendering CanvasJS server side so I'm not sure specifically where it fails without digging into it's code, but it looks like the units library is intended to only run in a browser. It looks like others experienced this and created an issue with the units library. |
Oh, this is not good... I'm currently on vacation and have very limited internet and time to devote to this... Is it a speechify can unit that triggers it, it seems like the tests where working, maybe we missed something 🤔 |
Hmm, it seems like this is only for the |
The regex didn't even match |
The dependency that caused this was removed a few weeks ago. Are you still having this problem with 2.0.0-alpha.5? |
Hmm, this is probably still a problem in 1.x 🤔 If anyone wants to backport #944 to 1.x I'd be happy to merge it :) |
@LinusU I'm having a similar issue with 1.6.7, units-css seems to do some DOM stuff: /Users/saschagehlich/development/node/node-videorenderer/node_modules/units-css/lib/utilities.js:39
parent.appendChild(element);
^
TypeError: Cannot read property 'appendChild' of undefined I see that the units-css dependency has been removed lately, but 1.6.8 or 1.7 have not been released yet. Any ETA on the release? Current 1.6.7 is basically broken. |
v1.6.8 was released on Dec 12. @saschagehlich let us know if you're still having issues after updating. |
It looks like commit #3d545056e2bb61b25f2d8bb1445c2e424a615163 that brought in units-css seems to break a fresh install for me, giving the following error:
I tried on multiple different node versions before realizing a recent commit was the issue - rolling back to the previous version seemed to fix it.
The text was updated successfully, but these errors were encountered: