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: backported disabled auto importing fiber on node >= 16 #1014

Merged
merged 1 commit into from Jan 14, 2022

Conversation

Morgul
Copy link

@Morgul Morgul commented Jan 14, 2022

Original Changes: 4ca004b

This PR contains a:

  • bugfix
  • new feature
  • code refactor
  • test update
  • typo fix
  • metadata update

Motivation / Use-Case

Backported the changes from 4ca004b to the 10.x line, so that projects stuck on Webpack 4 can still use Node v16.

Breaking Changes

Additional Info

There are unit test failures that seem unrelated to these changes, and the unit tests wouldn't run at all for me before them, so I'm unsure how to handle them.

Additionally, I'm not sure if the v10 branch is the correct one, let me know if this needs to be against a different branch.

@linux-foundation-easycla
Copy link

CLA Not Signed

@alexander-akait
Copy link
Member

Can you accept CLA?

@linux-foundation-easycla
Copy link

CLA Not Signed

@Morgul
Copy link
Author

Morgul commented Jan 14, 2022

Can you accept CLA?

Well, I've now filled it out twice, and it doesn't seem to have updated... I'm not sure what I'm missing?

Ah, it was the email on the commit. I believe that should now be associated with my account.

@Morgul
Copy link
Author

Morgul commented Jan 14, 2022

Turns out I had to just rewrite the author on the commit, and now it seems all good.

@alexander-akait alexander-akait merged commit f4234e4 into webpack-contrib:v10 Jan 14, 2022
@alexander-akait
Copy link
Member

Thanks

@alexander-akait
Copy link
Member

Released, try 10.2.1

@Morgul
Copy link
Author

Morgul commented Jan 14, 2022

It works perfectly!

@mariadb-ThienLy
Copy link

For some reason, we can only stick with v8.
Would it be possible to merge this to v8 then make a release for 8.0.3?
Thanks

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.

None yet

3 participants