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

perspective-webpack-plugin #399

Merged
merged 5 commits into from
Jan 28, 2019
Merged

perspective-webpack-plugin #399

merged 5 commits into from
Jan 28, 2019

Conversation

texodus
Copy link
Member

@texodus texodus commented Jan 28, 2019

Followup #398 into a refactor of the webpack build plugin into a new package, @jpmorganchase/perspective-webpack-plugin.

Reverts #391, which emits a double webpack manifest, and re-enables babel compilation in the plugin. Given the problems this has caused, I think an example of a real life problem this configuration causes is going to be necessary before we can consider further attempts to remove it.

Partially reverts #393, as the webpack 4 upgrade conflicts with yarn workspaces without a rebuild. This needs to be saved until the entire project can be upgraded.

@texodus texodus merged commit 9a95d8e into master Jan 28, 2019
@texodus texodus deleted the revert-webpack branch January 28, 2019 23:06
@LukeSheard
Copy link
Contributor

Given the problems this has caused

@texodus What were the problems this caused? I wasn't aware of anything in the unit tests and build testing I did.

I think an example of a real life problem this configuration causes is going to be necessary before we can consider further attempts to remove it.

Anything that sets the publicPath option on webpack breaks without the changes I was proposing. I can create a repo with an example of cross domain CDN caching with webpack and perspective.

webpack 4 upgrade conflicts with yarn workspaces without a rebuild

What does this mean? When I did a yarn it was fine.

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

Successfully merging this pull request may close these issues.

2 participants