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(init): fix webpack config scaffold in init package #1231

Merged
merged 1 commit into from
Feb 17, 2020

Conversation

anshumanv
Copy link
Member

fix webpack config scaffold

ISSUES CLOSED: #1230

What kind of change does this PR introduce?
bugfix, sync lock files

Did you add tests for your changes?
Yes

If relevant, did you update the documentation?
NA

Summary
Function to generate webpack config file was being skipped, fixed it.

Does this PR introduce a breaking change?
Fixes instead.

Other information

fix webpack config scaffold

ISSUES CLOSED: webpack#1230
@@ -130,8 +144,8 @@ export default function modifyHelperUtil(action: string, generator: typeof Gener

const successMessage = `\nYou can now run ${chalk.green(runCommand)} to bundle your application!\n\n`;
process.stdout.write(`\n${successMessage}`);
return;
Copy link
Member Author

Choose a reason for hiding this comment

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

We were exiting before actually creating the config.

@webpack-bot
Copy link

Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon.

Copy link
Contributor

@ematipico ematipico left a comment

Choose a reason for hiding this comment

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

It looks good but could you remove from the PR the lock files? That's strange there are so many changes

@anshumanv
Copy link
Member Author

Lock files seem out of sync and need to be updated eventually, should I do that in a separate PR @ematipico ?

@ematipico
Copy link
Contributor

That's strange because I don't get all these changes locally. Though, it would be better to do it on a separate PR

@anshumanv
Copy link
Member Author

Sounds good! Will push another commit.

That's strange because I don't get all these changes locally.

Can you try running npm run bootstrap? I got these when I did that I believe.

@ematipico
Copy link
Contributor

OK no problem, we will soon switch to yarn because we need workspaces feature in order to test different packages together

@ematipico ematipico merged commit 2dc495a into webpack:next Feb 17, 2020
@anshumanv anshumanv deleted the 1230 branch February 17, 2020 14:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[init]: invoking init command doesn't create a webpack config anymore
3 participants