Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR in [AssetsWebpackPlugin] Could not create output folder G:\WebStormWS\WebProTpl\dist\devServer\others #234

Closed
LP1994 opened this issue Jun 13, 2020 · 8 comments

Comments

@LP1994
Copy link

LP1994 commented Jun 13, 2020

assets-webpack-plugin: v5.0.0
node.js: v14.4.0
npm: v6.14.5
webpack: v4.43.0
webpack-dev-server: v3.11.0
Windows 10 professional edition 1902 18363.900

Describe the bug:
1、
ERROR in [AssetsWebpackPlugin] Could not create output folder G:\WebStormWS\WebProTpl\dist\devServer\others

To Reproduce:
1、The configuration of "webpack-dev-server" is:
...
writeToDisk: false,
......
image
2、The configuration of "assets-webpack-plugin" is:
......
useCompilerPath: false,
keepInMemory: true,
path: path.resolve( __dirname, ./dist/devServer/others/ ),
......
image
Uploading image.png…

Expected behavior:
Compilation successful!!!

PS:
However, "assets-webback-plugin v3.9.12" will not report the above mentioned errors.It can be compiled and run successfully.

@ztoben
Copy link
Owner

ztoben commented Jun 14, 2020

Okay, so you have writeToDisk off and it looks like it's still trying to write to a directory. Is that accurate?

@LP1994
Copy link
Author

LP1994 commented Jun 14, 2020

Okay, so you have writeToDisk off and it looks like it's still trying to write to a directory. Is that accurate?

Yes,I'm sure.
But!!!
"assets-webpack-plugin": "^3.9.12"!!!
There will be no bug mentioned above!!!

@ztoben
Copy link
Owner

ztoben commented Jun 15, 2020

Okay, I see the issue. The keepInMemory option was broken when we updated mkdirp. I'll get a fix out soon here.

@ztoben ztoben closed this as completed in 10c32f9 Jun 15, 2020
@ztoben
Copy link
Owner

ztoben commented Jun 15, 2020

@LP1994 Please verify that 5.0.1 works for you, but this should be fixed now. Thanks for the report!

@LP1994
Copy link
Author

LP1994 commented Jun 16, 2020

@LP1994 Please verify that 5.0.1 works for you, but this should be fixed now. Thanks for the report!

Hello.It's a mistake.
image

@ztoben
Copy link
Owner

ztoben commented Jun 16, 2020

@LP1994 Ah, I see what I did wrong. Can you try v5.0.2?

@LP1994
Copy link
Author

LP1994 commented Jun 16, 2020

@LP1994 Ah, I see what I did wrong. Can you try v5.0.2?

OK, I'll try the latest version of 5.0.2. If it succeeds, I'll let you know. Thank you for your prompt reply.

@LP1994
Copy link
Author

LP1994 commented Jun 16, 2020

@LP1994 Ah, I see what I did wrong. Can you try v5.0.2?

Hello, the latest version has been compiled successfully. Thank you for your timely feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants