diff --git a/.changepacks/changepack_log_plugin_core.json b/.changepacks/changepack_log_plugin_core.json new file mode 100644 index 000000000..5a3d13085 --- /dev/null +++ b/.changepacks/changepack_log_plugin_core.json @@ -0,0 +1,12 @@ +{ + "changes": { + "packages/plugin-utils/package.json": "Patch", + "packages/vite-plugin/package.json": "Patch", + "packages/webpack-plugin/package.json": "Patch", + "packages/rsbuild-plugin/package.json": "Patch", + "packages/bun-plugin/package.json": "Patch", + "packages/next-plugin/package.json": "Patch" + }, + "note": "Compile `.mts`, `.cts` and `.cjs` modules in every plugin, Turbopack and the import graph, and resolve `./a.js`, `./a.mjs` and `./a.cjs` imports to their TypeScript sources. Resolve package `exports` in the package's own order with the conditions of the bundler: Vite's `resolve.conditions`, the ESM conditions of webpack and Rspack per environment, and the target and `conditions` of Bun. Atom hoisting in webpack and Rsbuild plans over the `src` and `app` directories of the working directory and of the bundler root, not `src` alone. Bun keeps the modules whose values a file inlines in its module graph, so changing one rebuilds the file, and bundles the project's own `.js` and `.cjs` modules. No new build errors.", + "date": "2026-11-15T00:00:00.000Z" +} diff --git a/apps/landing/src/app/(detail)/docs/limitations/page.mdx b/apps/landing/src/app/(detail)/docs/limitations/page.mdx index 35ceefa35..81e697a6b 100644 --- a/apps/landing/src/app/(detail)/docs/limitations/page.mdx +++ b/apps/landing/src/app/(detail)/docs/limitations/page.mdx @@ -101,7 +101,7 @@ A dynamic value such as `width` becomes a CSS variable set in `style`, so a comp - An `.mdx` file is extracted after your MDX plugin compiles it to JavaScript, never as raw MDX. The Vite (`@mdx-js/rollup`), webpack and Rsbuild (`@mdx-js/loader`, `@rsbuild/plugin-mdx`) plugins and Next.js with webpack (`@next/mdx`) run their MDX step in a later phase: Vite in a `post` transform, webpack and Rsbuild in a `post` loader. Next.js with Turbopack and the Bun plugin do not extract MDX yet. The scan that reserves class names before a build reads JavaScript and TypeScript modules only, so a document's own classes are named when it compiles. Put components that need Devup UI styles in a `.tsx` module and use them from the document. - The plugins read `jsxImportSource` from the `tsconfig.json` (or `jsconfig.json`) in the working directory. Opt out with `importAliases: { '@emotion/react/jsx-runtime': false }`. - The outermost `ThemeProvider` also declares its theme on `:root`, in a `