-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
setup v9 transpilation to be based on browser support minbar #26170
Comments
we are currently blocked by #26251 |
we have a workaround for #26251, but based on partner browser compliance we cannot use browserlist yet. should be revisited by the end of year |
Because this issue has not had activity for over 180 days, we're automatically closing it for house-keeping purposes. Still require assistance? Please, create a new issue with up-to date details. |
1 similar comment
Because this issue has not had activity for over 180 days, we're automatically closing it for house-keeping purposes. Still require assistance? Please, create a new issue with up-to date details. |
This issue has not had activity for over 180 days! We're adding Soft close label and will close it soon for house-keeping purposes. |
1 similar comment
This issue has not had activity for over 180 days! We're adding Soft close label and will close it soon for house-keeping purposes. |
keep open |
ISSUE
Migrate v9 transpilation tooling to be based on browser support matrix. Use either
swc
orbabel
to replacets
transpilation to esm and commonjs.Steps:
migrate-converged-pkg
generator to add an.swcrc
file to each v9 package which will containbrowserlist
data based on the full browser support matrix of v9. feat(tools): scripts and generator updates to enable SWC transpilation for v9 packages #26527build:react-components
just-task to be used by v9 packages. The key difference here and the normalbuild
task is that this now splits up transpilation and api-generation as two separate tasks. The transpilation portion uses SWC to transpile code down and then makes use ofbabel
to transform griffel related code. Transpiling tocjs
oramd
will now use the already transpiledesm
code output from SWC as a workaround to the issue where ourgriffel
babel-preset is unable to directly parsecjs
code transpiled by SWC (tracking PR of ongoing work for this). This method allows for@griffel/babel-preset
to still parse code as expected since it has no trouble transformingesm
transpiled code from SWC. feat(tools): scripts and generator updates to enable SWC transpilation for v9 packages #26527swc
transpilation. chore(v9 packages): Migrate to SWC transpilation approach #27250Export. Fix issue causingwithFluentProvider
from@fluentui/react-storybook-addon
package and explicitly declare it in the@fluentui/vr-tests-react-components
storybookpreview.js
file so that the decorator is applied when storybook compiles viabuild-storybook
script (comment where this workaround was discovered in test)@fluentui/storybook-addon
to not be properly applied duringbuild-storybook
script feat(scripts-storybook): unify workspace addon loading for dev and prod builds #27006puppeteer
to v19 to mitigate unresponsive perf-tests: chore: prerequisite changes before migrating v9 packages to SWC based transpilation #26965create-package
templates. chore (scripts): update create-package plop templates to use swc/helpers in deps #27286Long term:
es2019
.swcrc
files to use browser matrix target. chore(v9 packages): Migrate to SWC browser matrix based transpilation #27036The text was updated successfully, but these errors were encountered: