Cannot find module error on Windows
See original GitHub issueFollowing getting started (https://peeky.netlify.app/guide/#our-first-test), I am getting Cannot find module
Cannot find module 'c:\Projects\peeky\src\test-gOdPlmAKc.js'
Require stack:
- c:\Projects\peeky\node_modules\@peeky\runner\dist\worker.js
Note that the spec file is in c:\Projects\peeky\src\example.spec.js, there is no test-gOdPlmAKc.js file.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:11 (5 by maintainers)
Top Results From Across the Web
How do I resolve "Cannot find module" error using Node.js?
This happens when a first npm install has crashed for some reason (SIGINT of npm), or that the delay was too long, or...
Read more >How to resolve "Cannot find module" error in Node - Sabe.io
To fix the Cannot find module error, simply install the missing modules using npm . To so, you can use the following command:...
Read more >Error: Cannot find module 'node-windows' #57 - GitHub
This sounds like a path problem with your node/npm install. All reactions.
Read more >Cannot find module 'X' error in Node.js | bobbyhadz
To solve the "Cannot find module" error in Node.js, make sure to install the package from the error message if it's a third-party...
Read more >How to resolve can't find module error in Node.js - Reactgo
To fix Cannot find module errors, install the modules properly by running a npm install command in the appropriate directory as your project's ......
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 FreeTop 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
Top GitHub Comments
I didn’t test peeky on Windows yet 🐈 (Ofc it had to not work on Windows 🤦 )
The build and execute pipeline has been completely reworked with Vite. Please try again and let me know if the issue is still present.