Skip to content

RC 2026-05-11 #291

Description

@rmenner

In this release

  • 9e5bca6 fix(build): error on unresolved imports in demo bundles
    • Convert Rollup's UNRESOLVED_IMPORT warning into a hard build error.Previously a missing workspace dep (e.g. a sibling component not yetbuilt) was silently externalized, leaving a bare specifier in thedemo .min.js that the browser rejected at runtime. Now the buildfails loudly with a pointer to fix the build order.- 3b29a21 fix(build): resolve hoisted workspace packages in demo bundles
    • Demo entries importing workspace packages (e.g. @aurodesignsystem/auro-datepicker)were sometimes left as bare specifiers in the output, causing the browserto throw "Failed to resolve module specifier" at runtime. nodeResolve'sauto-walkup didn't reach the hoist root in some monorepo / symlinkedworkspace setups.Pass MODULE_DIRS as absolute modulePaths to nodeResolve so it fallsback to the same parent node_modules chain the SCSS importer alreadyuses, ensuring hoisted deps get inlined into each .min.js.- 6b57f98 fix(build): isolate demo bundles and bump @actions/github
    • Demo entries that imported common modules caused Rollup to emit sharedchunks like index2.min.js, breaking demo HTML which only loads.min.js. Each demo entry now builds as its own Rollup pass withinlineDynamicImports so shared imports duplicate into each.min.js instead of spilling into a separate chunk.Also bumps @actions/github to ^9.1.1 and @rollup/plugin-terser to^1.0.0, and updates github-labels.ts to the new namespace import shape.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions