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

cleanup webpacks #396

Merged
merged 1 commit into from
Apr 11, 2019
Merged

cleanup webpacks #396

merged 1 commit into from
Apr 11, 2019

Conversation

SebastienGllmt
Copy link
Contributor

@SebastienGllmt SebastienGllmt commented Apr 10, 2019

Had to learn the webpack configs to do #386 so I decided to do some cleanup at the same time too. Basically we had a bunch of webpack files which were all copy/pastes of each other with one string changes so I simplified it to just two: prod and dev

Note: this is unrelated to the dev:mainnet issue since to fix that we need to fixup the way we handle manifest files.

Note: This PR is on a long chain of dependencies and not on develop so be careful about merging it. I made this a separate PR from #386 to make the diff easier to read.

@SebastienGllmt SebastienGllmt added the NFC No Functional Change (pure refactoring/cleanup) label Apr 10, 2019
@SebastienGllmt SebastienGllmt force-pushed the feature/bundle_optimize branch 2 times, most recently from b1a26ba to 287b7a9 Compare April 11, 2019 13:25
@vsubhuman vsubhuman changed the base branch from feature/bundle_optimize to develop April 11, 2019 13:55
@@ -11,4 +11,4 @@ tasks.copyAssets('build', argv.env);
console.log('[Webpack Build]');
console.log('-'.repeat(80));

exec(`./node_modules/.bin/webpack --config webpack/${argv.env}.config.js --progress --profile --colors`);
exec(`./node_modules/.bin/webpack --config webpack/prodConfig.js --progress --profile --colors --env=${argv.env}`);
Copy link
Contributor

Choose a reason for hiding this comment

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

So I don't get it, why we always use prodConfig? Even when env might be dev

Copy link
Contributor Author

Choose a reason for hiding this comment

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

the build.js is purely for production builds.

The dev environment has absolutely nothing to do with development builds. Having a network type dev was all a hack used in Icarus to get it to load up the right manifest file that allows connection to localhost.

@vsubhuman vsubhuman merged commit 0485c50 into develop Apr 11, 2019
@SebastienGllmt SebastienGllmt deleted the cleanup/webpack branch April 12, 2019 23:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NFC No Functional Change (pure refactoring/cleanup)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants