-
-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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
Combination of devtool: 'source-map' and library: ['Foo', '[name]'] throws error #6634
Comments
After some investigation, it seems the error is originally thrown in lib/SourceMapDevToolPlugin.js:59. It seems that options.namespace is expected to be a string, but is getting the value of output.library which is an array in this case. As the docs state that an array is an acceptable value of output.library, perhaps there is a missing conversion step before this line is reached? |
@tmilloff Where does it says that |
Ah, you're right. It appears it's not actually in the documentation, but it is in this examples page https://github.com/webpack/webpack/tree/master/examples/multi-part-library |
Yep, just saw it, Can you try adding filename option: |
Just tried it. I'm still seeing the same error with that addition. |
Array for |
I am still facing this issue when I have a library config with different names per target: This configuration from example here :
Throws the same error for me:
Would you like me to create a new issue for this ? |
@lorefnon check you |
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
With the following configuration, webpack throws the following error
If the current behavior is a bug, please provide the steps to reproduce.
The proceeding config is enough to produce the issue.
What is the expected behavior?
The proceeding config should build without issue, as was the case with versions prior to 4.
If this is a feature request, what is motivation or use case for changing the behavior?
N/A
Please mention other relevant information such as the browser version, Node.js version, webpack version, and Operating System.
4.0.1 (Previously working on 3.8.1)
The text was updated successfully, but these errors were encountered: