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 configuration wizard on release #12655

Merged
merged 4 commits into from
Apr 12, 2019
Merged

Conversation

atimmer
Copy link
Contributor

@atimmer atimmer commented Apr 11, 2019

Summary

This PR can be summarized in the following changelog entry:

  • N/A

The configuration wizard was broken when running grunt release build. This has been fixed with this PR. Also other issues should be fixed with this.

Relevant technical choices:

Test instructions

This PR can be tested by following these steps:

  • Create a zip using grunt artifact.
  • Test this zip in a clean installation
  • The configuration wizard should work.

UI changes

  • This PR changes the UI in the plugin. I have added the 'UI change' label to this PR.

Quality assurance

  • I have tested this code to the best of my abilities
  • I have added unittests to verify the code works as intended

Fixes #12636
Fixes #12641

When two different multi-builds of webpack use the same commons chunk
they will go wrong because of the module cache. This results in all
kinds of bugs.
We need to babelify parse5, because it contains code that isn't IE11
compatible. And they don't publish a babelified bundle.
@Djennez
Copy link
Member

Djennez commented Apr 11, 2019

Testing done for #12636 and #12641. Both are fixed when this PR is applied. Tested on Chrome (Mac OS) and IE11 (Windows 10 VM) on an empty WordPress 5.1.1 site.

Take care to reset node_modules/ before building.

@atimmer atimmer merged commit f17af27 into trunk Apr 12, 2019
@atimmer atimmer deleted the fix-configuration-wizard-on-release branch April 12, 2019 09:38
@atimmer atimmer added this to the 11.1 milestone Apr 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants