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

Handle when webpack config erroneously contains an entry point. #458

Closed
codymikol opened this issue Jan 6, 2021 · 0 comments
Closed

Handle when webpack config erroneously contains an entry point. #458

codymikol opened this issue Jan 6, 2021 · 0 comments

Comments

@codymikol
Copy link
Owner

Feature Proposal

When the specified webpack.config contains an entry field, this will overwrite the intended entry field before the internal configuration is merged with the passed webpack.config causing karma-webpack to throw an error and fail.

Since this is something that should never be specified as outlined by the README, we should log a warning if the field is set specifying that it should not be set and that it will be ignored.

We should then delete the entry field before calling webpack-merge to ensure a successful run.

Feature Use Case

Prevent unnecessary failures and give the user feedback about invalid configuration.

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

No branches or pull requests

1 participant