Building 🏗 https://turnshift.app, Shift Scheduling for Slack Teams.
Also:
https://nextjsnews.com
https://github.com/vvo
https://dev.to/vvo
Before: JavaScript and support
@algolia
.
Definitely right. When that's the case I am not sure if there's even a solution. Do you know one? If the library tries to read directly from the window object, then it just isn't compatible with Node.js (even if it could I guess).
Maybe you can do something like global.window = {} and provide the necessary code? Let us know!
Building 🏗 https://turnshift.app, Shift Scheduling for Slack Teams.
Also:
https://nextjsnews.com
https://github.com/vvo
https://dev.to/vvo
Before: JavaScript and support
@algolia
.
Building 🏗 https://turnshift.app, Shift Scheduling for Slack Teams.
Also:
https://nextjsnews.com
https://github.com/vvo
https://dev.to/vvo
Before: JavaScript and support
@algolia
.
Hey Justin, don't, because I am updating the article right now to add that this particular solution works well for libraries you're importing :) Thanks for the tip!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
none of these solutions work well if the problem is in a library you are using
Definitely right. When that's the case I am not sure if there's even a solution. Do you know one? If the library tries to read directly from the window object, then it just isn't compatible with Node.js (even if it could I guess).
Maybe you can do something like global.window = {} and provide the necessary code? Let us know!
My solution was to import the component that used the library that used
window
using the dynamic importerThanks, if I am not mistaken, that's the third solution of this current blog post: dev.to/vvo/how-to-solve-window-is-...
I feel silly now.
Lol!!
Hey Justin, don't, because I am updating the article right now to add that this particular solution works well for libraries you're importing :) Thanks for the tip!