Fix tsup configuration for vanilla Webpack 4 without babel-loader#5322
Merged
Conversation
babel-loader
OEvgeny
approved these changes
Oct 9, 2024
Collaborator
OEvgeny
left a comment
There was a problem hiding this comment.
Looks good. Who the hell is using Webpack 4 without any preloader in 2024? It kind of kills progress of the past ~4 years in web development.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changelog Entry
Fixed
babel-loader, by @compulim, in PR #5322Description
There are some limitations on vanilla Webpack 4 without
babel-loader:noExternal: 'globalize'only for ESMglobalizeis CJS-only, we bundle it inside Web Chat so it don't do "ESM -> CJS"??operator.js, otherwise, Webpack 4 may point to.mjswhich will require BabelAlso, in
tsup, it disabled code splitting for CJS asesbuilddoes not support it. We are using experimental flag to re-enable it.Design
Specific Changes
globalizeonly in ESM but not CJSglobalizeis CJS only and it would cross the ESM -> CJS boundarybotframework-webchat-[api|component]/[decorator|internal]I have added tests and executed them locallyCHANGELOG.mdI have updated documentationReview Checklist
Accessibility reviewed (tab order, content readability, alt text, color contrast)Browser and platform compatibilities reviewedCSS styles reviewed (minimal rules, noz-index)Documents reviewed (docs, samples, live demo)Internationalization reviewed (strings, unit formatting)package.jsonandpackage-lock.jsonreviewedSecurity reviewed (no data URIs, check for nonce leak)Tests reviewed (coverage, legitimacy)