8000 fix(webpack): use default export from webpack by danielroe Β· Pull Request #19166 Β· nuxt/nuxt Β· GitHub
[go: up one dir, main page]

Skip to content

fix(webpack): use default export from webpack#19166

Merged
danielroe merged 1 commit intomainfrom
fix/webpack-cjs
Feb 20, 2023
Merged

fix(webpack): use default export from webpack#19166
danielroe merged 1 commit intomainfrom
fix/webpack-cjs

Conversation

@danielroe
Copy link
Member

πŸ”— Linked issue

resolves #19141

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

This change how webpack is imported to avoid an issue with importing webpack into a node esm package.

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@codesandbox
Copy link
codesandbox bot commented Feb 20, 2023

CodeSandbox logoCodeSandbox logoΒ  Open in CodeSandbox Web Editor | VS Code | VS Code Insiders

@danielroe danielroe merged commit d2481f9 into main Feb 20, 2023
@danielroe danielroe deleted the fix/webpack-cjs branch February 20, 2023 20:34
@danielroe danielroe mentioned this pull request Feb 27, 2023
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.

Not able to use webpack as builder

1 participant

0