Preparation before removing babel plugins - adding import extensions and displayName manually

[joyenjoyer]

Summary

This PR prepares the removal of Babel and Babel plugins. It writes two things into the source that Babel plugins inject today: explicit relative-import extensions and static displayNames. It also adds minimal webpack config so our own toolchains resolve the new specifiers.

No transpiler change. Babel still runs, with the same plugins. The plugins are idempotent. They skip a specifier already ending in .js. They skip a class that already has a displayName. So the compiled es/ and lib/ output stays semantically identical to master.

This keeps master releasable. It also makes the later SWC safe.

This is PR1 of a 3-PR stack:

• PR1 (this one) — source prep, no transpiler change. Non-breaking.
• PR2 — swap babel-loader → swc-loader in the Cypress + docs webpack builds. Library build still Babel. Nothing published changes.
• PR3 — ESM-only library build on SWC, and remove Babel + its plugins. The breaking PR.

What changed (3 commits)

1. add explicit import extensions to relative specifiers — appends .js (or /index.js for directory imports) to relative import / export ... from specifiers. Reproduces babel-plugin-add-import-extension. Relative specifiers only. Bare/package and type-only imports are untouched.
2. add static displayName to component classes — adds static displayName = '<ClassName>' to React class components that lack one. Reproduces babel-plugin-add-displayname-for-react. It is idempotent: it skips classes that already have one, and any class without a render method. This includes the __docs__ app. Its Babel config (packages/__docs__/babel.config.js) uses @instructure/ui-babel-preset, which runs add-displayname-for-react unconditionally. So Babel was already injecting displayName into the docs' class components at build time. Writing it into the source keeps that behavior identical once Babel is removed in PR3.
3. resolve .js specifiers to TypeScript source in webpack — adds resolve.extensionAlias (.js → .ts/.tsx) to the Cypress config and the shared ui-webpack-config. This lets webpack builds that bundle the .ts/.tsx source directly (Cypress, docs) resolve the new .js specifiers. It is a consequence of the source change, so it lives here.

What is intentionally NOT in this PR

• Removing the Babel plugins. They stay until PR3. Removing them here would change build output. It would also break the ESM output of generated files (ui-icons/src/generated, ui-themes tokens). Those are generated/gitignored, so the source edits can't cover them. Generator updates will be in a later PR.

Compiled-output deltas vs master

All behavior-preserving:

• ESM (es/) — cosmetic codegen only. Semantically identical. The possible differences are:
  • Quote style — a specifier emitted with single quotes vs double quotes (e.g. "./useStyle.js" → './useStyle.js').
  • Blank lines — an added or removed empty line between statements.
  • Comment placement — a leading comment attached to a slightly different line.
  • Line wrapping — a long import/export wrapped across lines vs kept on one line.
  • Trailing commas / whitespace — minor punctuation or indentation noise from the codegen path.
• CJS (lib/) — the added .js specifiers, plus the require binding names Babel derives from them. Behavior-preserving. They disappear once PR3 drops the lib/ build.

How to test?

• Run commands (bootstrap, test, dev)
• Spot check file in es folders, compare it to latest master
• Use Balazs' diff tool or another comparison script but keep in mind there will be changes (read the Compiled-output deltas vs master above), it is only an issue if the two files are not semantically identical

[Copilot]

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

[github-actions]

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-06-11 11:39 UTC

[github-actions]

Visual regression report

✅ No changes.

Status	Count
Unchanged	32
Changed	0
New	0
Removed	0

📊 View full report

_{Baselines come from the visual-baselines branch. They refresh on every merge to master.}

[matyasf]

Will this also be need to be set for end users?

[joyenjoyer]

We only need this because Cypress and the docs build straight from our .ts source, so the new .js import extensions have to be pointed back at the real .ts/.tsx files. Consumers never hit this since they use the built es/ and lib/ output where those .js files actually exist.

[balzss]

overall looks and works well, great work! some minor comments:

• you added displaynames for the docs package components but didn't add the extensions for the imports there. is that intentional?
• you added explicit type resolution for the cypress config but not for vitest. i'm not sure it's bad if it's implicit but worth thinking about
• the commit msg scope is a bit misleading. they are build(swc) but swc migration was not done in those commits

[joyenjoyer]

overall looks and works well, great work! some minor comments:

• you added displaynames for the docs package components but didn't add the extensions for the imports there. is that intentional?
• you added explicit type resolution for the cypress config but not for vitest. i'm not sure it's bad if it's implicit but worth thinking about
• the commit msg scope is a bit misleading. they are build(swc) but swc migration was not done in those commits

1. yes, this is intentional. Babel plugins added displayname to components in the docs package but no extensions. I intend to keep it this way.
2. Vite already des .js->.ts rewrite natively, cypress project uses webpack that has to be configured manually
3. I will change that, thanks

@balzss

[matyasf]

looks good, I've checked it with the new diff tool