Cannot find module '../build/safe-execute'
See original GitHub issueHi, I want to debug preact, but when I run npm run test
got the following error:
13 02 2017 11:02:38.084:ERROR [plugin]: Error during loading "F:\workspace\preact\node_modules/karma-sauce-launcher" plugin:
Cannot find module '../build/safe-execute'
START:
13 02 2017 11:02:44.304:INFO [karma]: Karma v1.4.1 server started at http://0.0.0.0:9876/
13 02 2017 11:02:44.305:INFO [launcher]: Launching browser PhantomJS with concurrency 2
13 02 2017 11:02:44.306:ERROR [karma]: Found 1 load error
nodejs: v6.9.5-x64
I’m not sure it’s a Karma incompatibility with Windows? Can anyone know how to solve this? Thanks.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:7
- Comments:8
Top Results From Across the Web
How do I resolve "Cannot find module" error using Node.js?
it seems like when i installed it globally the npm/node-modules folder was empty and i was trying to use ng new project-name it...
Read more >Cacher is the code snippet organizer for pro developers
Fix for Karma Cannot find module '../build/safe-execute' error - @benjamincharity shared this Cacher snippet. Cacher is the code snippet ...
Read more >error ts2307: cannot find module or its corresponding type ...
When executing tsc on a project with dapr client version 2.0 and 2.0.1 the build process should raises a TS2307 error due to...
Read more >cannot find module [Node npm Error Solved] - freeCodeCamp
Why the "Error: cannot find module" Occurs · you're trying to import an item from a module you don't have installed in your...
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 had the same problem. I uninstalled and reinstalled wd npm uninstall wd npm install -D wd
It looks like this can occur from a corrupted cache of the
wd
module. It’s supposed to create../build/safe-execute
here: https://github.com/admc/wd/blob/b1463ce/scripts/build-browser-scripts.jsForcing a clean install of this module should resolve the issue. On travis I was able to resolve it by deleting my caches.