question-mark
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.

Relative modules were not found in Laravel-Mix 1.4.3

See original GitHub issue
  • Laravel Mix Version: 1.4.3 (npm list --depth=0)
  • Node Version (node -v): 8.5.0
  • NPM Version (npm -v): 5.4.2
  • OS: macOS 10.12.6 / Ubuntu 17.04

Description:

screen shot 2017-09-16 at 2 50 28 pm
ERROR  Failed to compile with 5 errors                                                                                                                                      
These relative modules were not found:

* ./components/Avatar.vue in ./resources/assets/js/frontend.js
* ./components/backend/FooterComponent.vue in ./resources/assets/js/backend.js
* ./components/passport/AuthorizedClients.vue in ./resources/assets/js/backend.js
* ./components/passport/Clients.vue in ./resources/assets/js/backend.js
* ./components/passport/PersonalAccessTokens.vue in ./resources/assets/js/backend.js

This error is not seen in Laravel Mix 1.4.2.

Steps To Reproduce:

Running the command npm run production or yarn production results in the build failing on Laravel Mix 1.4.3.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:23 (9 by maintainers)

github_iconTop GitHub Comments

3reactions
joshlewiscommented, Oct 10, 2017

The problem still exists. All these people above, including me, have tried to re-install with yarn and yarn run dev no longer works if they do. It only works with npm. This issue shouldn’t be closed just because you can’t reproduce the problem.

3reactions
IvanBernatoviccommented, Oct 10, 2017

@ruchern But in our case deleting node_modules doesn’t help, only solution is to install dependencies with npm install and running npm run dev. When we install dependencies with yarn install then npm run dev and yarn run dev don’t work. So far with Yarn version from 1.0 to 1.2 (latest stable) building fails, with 0.27.5 it works. If you want I can find out exact Yarn version when building assets started to fail?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Relative modules were not found in Laravel-Mix 1.4.3 #1195
This error is not seen in Laravel Mix 1.4.2 . Steps To Reproduce: Running the command npm run production or yarn production results...
Read more >
Laravel-mix modules were not found - Laracasts
Hi, as the title says it I cant get my css and js files compiled with laravel-mix because modules were not found. I...
Read more >
webpack - Laravel Mix: These dependencies were not found
Searching on GitHub, I found there is a bug in NPM 5.2.0 that affects Laravel Mix. Read more about it here. I had...
Read more >
@vue/composition-api - npm
Missing APIs. The following APIs introduced in Vue 3 are not available in this plugin. onRenderTracked; onRenderTriggered; isProxy ...
Read more >
[Solved]-Compile error [VueLoaderPlugin Error] vue-loader 15 ...
In this way you use the vuetify-loader after laravel-mix has done it's magic. ... compile with one error saying "this relative module module...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found