build(ios26): resolve ESM imports during compilation - #236
Conversation
Playwright test resultsDetails
|
|
📊 Ionic 9 Playwright Test Report View the detailed Ionic 9 report: https://rdlabo-dev.github.io/ionic-theme-ios27/pr-236/ Ionic 8 runs against the same screenshots in a separate matrix job. View both results in the workflow run. |
|
📊 Ionic 9 Playwright Test Report View the detailed Ionic 9 report: https://rdlabo-dev.github.io/ionic-theme-ios27/pr-236/ Ionic 8 runs against the same screenshots in a separate matrix job. View both results in the workflow run. |
|
📊 Ionic 9 Playwright Test Report View the detailed Ionic 9 report: https://rdlabo-dev.github.io/ionic-theme-ios27/pr-236/ Ionic 8 runs against the same screenshots in a separate matrix job. View both results in the workflow run. |
The iOS 26 theme's emitted ESM contained extensionless imports, so direct Node imports could fail. Keep TypeScript source imports extensionless, matching Ionic's source style, and resolve them automatically during the normal build.
@rdlabo/ionic-theme-utils@0.1.2for the sharedrdlabo-build-themeandrdlabo-check-esmCLIs.tsc --noEmitfor type checking and use tsdown to emit ESM JavaScript and declarations with resolved relative specifiers. Source files are unchanged; dependencies stay external and CSS output is preserved."type": "module", use TypeScript's bundler resolution mode, and rename the CommonJS Prettier configuration to.cjs.This follows the build-time approach discussed in #222. Shared tooling: rdlabo-dev/ionic-theme-utils#5.
Validation on Node 24.17.0:
skipLibCheck.Browser visual and native-device tests were not run locally for this build change.