-
-
Notifications
You must be signed in to change notification settings - Fork 8.8k
-
-
Notifications
You must be signed in to change notification settings - Fork 8.8k
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
webpackExclude doesn't work #9963
Comments
Your code only includes |
I think you're right. There is only one other place where I use a dynamic import. That is a sister component to const Loader = universal(
// $FlowFixMe
(props: { path: string }) =>
import(
`./${props.path}`
),
{
minDelay: 0,
loading: () => <i className="fa fa-spinner fa-spin" />,
}
); This was generating the following warning in my console:
And when I put the const Loader = universal(
import(
`./${props.path}`
),
{
minDelay: 0,
loading: () => <i className="fa fa-spinner fa-spin" />,
}
); |
This issue had no activity for at least three months. It's subject to automatic issue closing if there is no activity in the next 15 days. |
Issue was closed because of inactivity. If you think this is still a valid issue, please file a new issue with additional information. |
Reposting with corrected code
Bug report
What is the current behavior?
Given a dynamic import like this:
It does not exclude the files matching the pattern from the chunk generation. Here is a sample output from the
manifest.json
of the files that match the following pattern and are generated by this importWhat is the expected behavior?
It is expected to exclude these files from the manifest.
Other relevant information:
webpack version: 4.41.0
Node.js version: 8.x.x
Operating System: Mac OS
The text was updated successfully, but these errors were encountered: