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.

Prevent writing to file that only differs in casing or query string from already written file.

See original GitHub issue
  • Laravel Mix Version: 6.0.10 (npm list --depth=0)
  • Node Version (node -v): v14.12.0
  • NPM Version (npm -v): 6.14.8
  • OS: MacOS BigSur

Description:

After upgrading the laravel-mix, I have an error during the compilation (using npm run watch).

mix.js('resources/src/main.js', 'public/js').vue()
    .webpackConfig({
        resolve: {
            alias: {
                '@': path.resolve(__dirname, 'resources/src'),
            }
        }
    });
mix.sass('resources/src/scss/style.scss', 'public/css');
mix.copy('resources/src/assets/images/logo/', 'public/images/');

I’m using an image bg.png in the Vue files and in the SCSS file. I think the problem come from here. What can I do to “skip” or “silent” this error ? Or just solve it ?

Steps To Reproduce:

npm run watch

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5

github_iconTop GitHub Comments

7reactions
thecrypticacecommented, Apr 21, 2021

This error occurs when you import files with different casing In your compiled JS that cause chunks to get created with different casing. For instance if you have dynamic imports for the same file but use a webpackChunkName that differs in the casing this error will be thrown. This is not a Mix issue but an issue with imports in your JS or in your webpack.mix.js file where you provide the same file name but mixed casing for resources.

2reactions
dducrocommented, May 30, 2021

The same error is also thrown if they’re multiple images with the same name in separate folders. When compiling vue with mix 6 the images are copied to one directory named images. That seems to cause this issue. Any idea to disable this?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Error: Prevent writing to file that only differs in casing or query ...
I am working on a laravel reactjs project and when I run the command npm run dev the compilation stuck at 95% and...
Read more >
Prevent writing to file that only differs in casing or query string ...
This error occurs when you import files with different casing In your compiled JS that cause chunks to get created with different casing....
Read more >
Prevent writing to file that only differs in casing or query string ...
Prevent writing to file that only differs in casing or query string from already written file.
Read more >
Prevent writing to file that only differs in casing or query string ...
Coding example for the question Error: Prevent writing to file that only differs in casing or query string from already written file. reactjs ......
Read more >
Filename only differs in already included file only in casing.
Using TypeScript 2.5.3, WebStorm displays errors in the import statements. It shows TS1149 error. WS-183.4284.130, JRE 1.8.0_152-release-1343-b15x64 ...
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