Error: Cannot find module 'window'
See original GitHub issueI’m using this module in a browserify project and getting the following error when I try and build:
Error: Cannot find module 'window' from '[path to project]/node_modules/is-in-viewport/lib'
I’m including the plugin after I include jQuery, and jquery is a available as a module with the correct name:
var jQuery = $ = require('jquery');
require('is-in-viewport');
Any thoughts on what might be going on here?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:20
- Comments:6 (3 by maintainers)
Top Results From Across the Web
node.js - Nodejs cannot find installed module on Windows
The answer for windows 10 is to set the NODE_PATH in the enviroment variables with C:\Users\User\node_modules. Share.
Read more >Error Nodejs cannot find installed module on Windows
I am learning nodejs at the moment on Windows. Several modules are installed globally with npm.cmd, and nodejs failed to find the installed ......
Read more >cannot find module [Node npm Error Solved] - freeCodeCamp
When you get the “cannot find module” error, or “module not found”, it means you've not installed the package you're trying to use....
Read more >node-windows - npm
node-windows does not use native modules. There are some binary/exe utilities, but everything needed to run more complex tasks is packaged ...
Read more >Error on starting computer - Cannot find module
Original Title - have an error when starting my computer running on windows 7 : can not find module- user\appdata\roming\KBDIULAT6.dll.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
version 2.4.2 works fine Now trying 3.0.4 upd: yes, it’s alright now 😃 Thank you!
@sapolio @andyinabox @ForkInSpace Could you folks try version
3.0.4
please? It should fix this issue once and for all.