version 4.4.1 not compiling
See original GitHub issueDescription Upgrading to 4.4.1 causes all builds to fail due to the following:
[webpack-cli] Error: ENOENT: no such file or directory, open 'C:\wamp64\www\_unseen\frontend-boilerplate\test\dist\images\svgsprite.svg'
at Object.openSync (node:fs:585:3)
at Object.readFileSync (node:fs:453:35)
at File.read (C:\wamp64\www\_unseen\frontend-boilerplate\node_modules\laravel-mix\src\File.js:227:19)
at File.version (C:\wamp64\www\_unseen\frontend-boilerplate\node_modules\laravel-mix\src\File.js:234:25)
at Manifest.hash (C:\wamp64\www\_unseen\frontend-boilerplate\node_modules\laravel-mix\src\Manifest.js:61:74)
at C:\wamp64\www\_unseen\frontend-boilerplate\node_modules\laravel-mix\src\webpackPlugins\CustomTasksPlugin.js:118:31
at Collection.each (C:\wamp64\www\_unseen\frontend-boilerplate\node_modules\collect.js\dist\methods\each.js:18:14)
at CustomTasksPlugin.applyVersioning (C:\wamp64\www\_unseen\frontend-boilerplate\node_modules\laravel-mix\src\webpackPlugins\CustomTasksPlugin.js:117:42)
at C:\wamp64\www\_unseen\frontend-boilerplate\node_modules\laravel-mix\src\webpackPlugins\CustomTasksPlugin.js:23:22 {
errno: -4058,
syscall: 'open',
code: 'ENOENT',
path: 'C:\\wamp64\\www\\_unseen\\frontend-boilerplate\\test\\dist\\images\\svgsprite.svg'
}
Rolling back to 4.4.0 compiles correctly.
Webpack config
new SVGSpritemapPlugin(src('svg-sprite/*.svg'), {
output: {
filename: 'images/svgsprite.svg',
chunk: { keep: true },
svgo: {
plugins: [
{
name: 'addClassesToSVGElement',
params: {
className: 'svg-sprite'
}
}
]
}
},
sprite: { prefix: false }
})
System information
System:
OS: Windows 10 10.0.22000
CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700KF
Memory: 43.30 GB / 63.86 GB
Binaries:
Node: 16.14.0 - C:\Program Files\nodejs\node.EXE
npm: 8.3.1 - C:\Program Files\nodejs\npm.CMD
npmPackages:
@ashthornton/asscroll: ^2.0.7 => 2.0.7
@babel/eslint-parser: ^7.18.2 => 7.18.2
@babel/preset-env: ^7.18.2 => 7.18.2
@unseenco/e: ^2.2.2 => 2.2.2
@unseenco/taxi: ^0.6.0 => 0.6.0
browser-sync: ^2.27.10 => 2.27.10
browser-sync-webpack-plugin: ^2.3.0 => 2.3.0
core-js: ^3.23.2 => 3.23.2
eslint: ^8.18.0 => 8.18.0
eslint-config-standard: ^17.0.0 => 17.0.0
eslint-plugin-import: ^2.26.0 => 2.26.0
eslint-plugin-node: ^11.1.0 => 11.1.0
eslint-plugin-promise: ^6.0.0 => 6.0.0
eslint-webpack-plugin: ^3.1.1 => 3.1.1
glslify: ^7.1.1 => 7.1.1
glslify-loader: ^2.0.0 => 2.0.0
gsap: ^3.10.4 => 3.10.4
laravel-mix: ^6.0.43 => 6.0.43
laravel-mix-polyfill: ^3.0.1 => 3.0.1
laravel-mix-purgecss: ^6.0.0 => 6.0.0
postcss: ^8.4.14 => 8.4.14
purgecss-with-wordpress: ^4.1.0 => 4.1.0
raw-loader: ^4.0.2 => 4.0.2
resolve-url-loader: ^5.0.0 => 5.0.0
sass: ^1.52.3 => 1.52.3
sass-loader: ^12.6.0 => 12.6.0
stylelint: ^14.9.1 => 14.9.1
stylelint-config-sass-guidelines: ^9.0.1 => 9.0.1
stylelint-webpack-plugin: ^3.3.0 => 3.3.0
svg-spritemap-webpack-plugin: 4.4.1 => 4.4.1
Additional context
Issue Analytics
- State:
- Created a year ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Unable to update compiler to version 4.4.1 - Code Composer ...
HI,. I have updated my msp430 compiler in CCS but its still showing 4.3.5 version only. When i click on check for updates...
Read more >CR BASIC Could not compile after 4.4 update
Hi,. We have loggernet 4.3. We can compile crbasic programs without any problem. When we update it to 4.4 it stops compiling and...
Read more >The JDK 18.0.1 isn't compatible with Gradle 4.4.1
That project uses a very old version of Gradle which is not compatible with Java 18. I can see in the file gradle-wrapper....
Read more >Compile error with Webpack 5 after upgrading but working ...
I have searched the issues of this repository and believe that this is not a duplicate.
Read more >WRF Self Install Scripts (WRF Version 4.4.1)
Note: The only compilation requirements for the idealized capability are WPS and WRF. If desired, UPP may also be used. The components MPIPOM-TC ......
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
Are you able to provide a minimal reproduction repository so that I can debug this a bit?
Great, I’ve just published
4.4.2
to npm. Thanks for testing/investigating! ❤️