Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Dependency was not found in node_modules
See original GitHub issueI get the following errors every time that I try to run npm run dev.
vagrant@data-ms:~/data-ms$ npm run dev -ddd
npm info it worked if it ends with ok
npm verb cli [ '/usr/bin/nodejs', '/usr/bin/npm', 'run', 'dev', '-ddd' ]
npm info using npm@3.10.8
npm info using node@v6.9.1
npm verb run-script [ 'predev', 'dev', 'postdev' ]
npm info lifecycle @~predev: @
npm sill lifecycle @~predev: no script for predev, continuing
npm info lifecycle @~dev: @
> @ dev /home/vagrant/data-ms
> cross-env NODE_ENV=development webpack --progress --config=node_modules/laravel-mix/setup/webpack.config.js
95% emit
ERROR Failed to compile with 1 errors
This dependency was not found in node_modules:
* /home/vagrant/data-ms/resources/assets/js/app.js
Did you forget to run npm install --save for it? Asset Size Chunks Chunk Names
/js/app.js 1.54 kB 0 [emitted] app
mix-manifest.json 32 bytes [emitted]
[0] multi app 28 bytes {0} [built] [1 error]
npm verb lifecycle @~dev: unsafe-perm in lifecycle true
npm verb lifecycle @~dev: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/vagrant/data-ms/node_modules/.bin:/home/vagrant/.composer/vendor/bin:/home/vagrant/bin:/home/vagrant/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
npm verb lifecycle @~dev: CWD: /home/vagrant/data-ms
npm sill lifecycle @~dev: Args: [ '-c',
npm sill lifecycle 'cross-env NODE_ENV=development webpack --progress --config=node_modules/laravel-mix/setup/webpack.config.js' ]
npm sill lifecycle @~dev: Returned: code: 0 signal: null
npm info lifecycle @~postdev: @
npm sill lifecycle @~postdev: no script for postdev, continuing
npm verb exit [ 0, true ]
npm info ok
app.js does exist at the specified location.
Issue Analytics
- State:
- Created 7 years ago
- Comments:12
Top Results From Across the Web
Dependency Not found even defined in package.json and ...
I took this debugging opportunity to learn more about npm and webpack. It looks like the creators of photo-sphere-viewer did not specify ...
Read more >"Dependencies were not found" - on npm run serve #4472
These dependencies were not found: C:\Users\Sepp\Documents\dev\Vue\testapp\node_modules\webpack-dev-server\client\index.js?
Read more >Dependency or package not found - DeployHQ
Dependency or package not found ... This might happen if you have a dependency that is being installed as a result of one...
Read more >getting the following error This dependency was not found: FS
When I run npm run dev. I am getting the following error. ERROR Failed to compile with 3 errors 22:07:39. This dependency was...
Read more >module-not-found - Next.js
The module you're trying to import is not installed in your dependencies ... When importing a module from npm this module has to...
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
It’s related to this:
You didn’t bind the
hrefattribute to anything. Remove the colon.Both lines are on lines with plain HTML