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

fix(package.json): Updating html-webpack-plugin, fixing compilation.m… #855

Closed
wants to merge 1 commit into from
Closed

fix(package.json): Updating html-webpack-plugin, fixing compilation.m… #855

wants to merge 1 commit into from

Conversation

boazhoch
Copy link

@boazhoch boazhoch commented Mar 5, 2018

fix(package.json): Updating html-webpack-plugin, fixing compilation.mainTemplate.applyPluginsWaterfall error, related to incompatible version between webpack 4 and html-webpack-plugin.

See issue here

…ainTemplate.applyPluginsWaterfall error realated to incompatible version between webpack 4 and html-webpack-plugin jantimon/html-webpack-plugin#841
Copy link
Contributor

@kontrollanten kontrollanten left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! I've tested your PR and it seems to work great.

kontrollanten added a commit to kontrollanten/algolia-places-react that referenced this pull request Mar 5, 2018
Copy link
Member

@sapegin sapegin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

It's a breaking change though, so we'll have to wait until the next major release.

@sapegin sapegin added this to the 7.0.0 milestone Mar 5, 2018
@boazhoch
Copy link
Author

boazhoch commented Mar 6, 2018

@sapegin Well it's a breaking change, but currently webpack 4 and react-styleguidist are incompatible, i would consider having a /next branch - anyway its for your consideration.

@sapegin
Copy link
Member

sapegin commented Mar 6, 2018

You can use this PR’s branch.

@okonet
Copy link
Member

okonet commented Mar 29, 2018

Why would we wait till next major release if this one is already a major one? Let's not get attached to version numbers, please. They are for machines.

@sapegin
Copy link
Member

sapegin commented Mar 29, 2018

We're going to get rid of the HTML plugin entirely — #896. But thanks for help anyway!

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.

4 participants