This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@open-pioneer/build-package@3.0.0
Major Changes
e4ae880: Switch to type: module
Minor Changes
e4ae880: Implement additional validations when importing modules from other packages.
When importing modules from normal node packages, build-package will now check that the imported module actually exists.
When importing modules from another trails package in the same repository, build-package now verifies that the imported module is an actual entry point of that package (declared in the build.config.mjs).
e4ae880: Implement automatic rewrite for certain problematic import statements.
Under certain conditions, build-package will add extensions to imported modules when the imported module does not (strictly) exist.
For example, this rewrites
import * from "ol/proj/proj4";
to
import * from "ol/proj/proj4.js";
While the first import works with bundlers such as Vite or Rollup, Node will refuse to import it.
Because node is strict about extensions, the first snippet cannot execute in some environments (such as Vitest).
e4ae880: Introduce an option to configure the root directory (-r for the CLI, rootDirectory for the JavaScript API).
The root directory is used to detect which packages are local to the project.
The option defaults to the root of the current workspace (e.g. the PNPM workspace root), or, if that doesn't work, to the root of the current git repository.
However, it can also be configured manually.
Patch Changes
3550ca8: Update dependencies
Updated dependencies [d9a0c1b]
@open-pioneer/build-common@2.0.4
@open-pioneer/build-package-cli@2.1.0
Minor Changes
e4ae880: Switch to type: module
e4ae880: Implement additional validations when importing modules from other packages.
When importing modules from normal node packages, build-package will now check that the imported module actually exists.
When importing modules from another trails package in the same repository, build-package now verifies that the imported module is an actual entry point of that package (declared in the build.config.mjs).
e4ae880: Introduce an option to configure the root directory (-r for the CLI, rootDirectory for the JavaScript API).
The root directory is used to detect which packages are local to the project.
The option defaults to the root of the current workspace (e.g. the PNPM workspace root), or, if that doesn't work, to the root of the current git repository.
However, it can also be configured manually.
Patch Changes
3550ca8: Update dependencies
Updated dependencies [e4ae880]
Updated dependencies [e4ae880]
Updated dependencies [3550ca8]
Updated dependencies [e4ae880]
Updated dependencies [e4ae880]
@open-pioneer/build-package@3.0.0
@open-pioneer/build-common@2.0.4
Patch Changes
d9a0c1b: Use timestamps instead of request ids to import build configs
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@open-pioneer/build-package@3.0.0
Major Changes
type: moduleMinor Changes
e4ae880: Implement additional validations when importing modules from other packages.
build-packagewill now check that the imported module actually exists.build-packagenow verifies that the imported module is an actual entry point of that package (declared in thebuild.config.mjs).These validations are designed to errors where a package would run locally (in Vite's development mode) but end up broken when published (see also https://github.com/open-pioneer/trails-core-packages/issues/42).
e4ae880: Implement automatic rewrite for certain problematic import statements.
Under certain conditions,
build-packagewill add extensions to imported modules when the imported module does not (strictly) exist. For example, this rewritesto
While the first import works with bundlers such as Vite or Rollup, Node will refuse to import it. Because node is strict about extensions, the first snippet cannot execute in some environments (such as Vitest).
This new behavior is intended as a fix for https://github.com/open-pioneer/trails-openlayers-base-packages/issues/314. Please open an issue if this fix causes any problems for your packages.
e4ae880: Introduce an option to configure the root directory (
-rfor the CLI,rootDirectoryfor the JavaScript API).The root directory is used to detect which packages are local to the project. The option defaults to the root of the current workspace (e.g. the PNPM workspace root), or, if that doesn't work, to the root of the current git repository. However, it can also be configured manually.
Patch Changes
@open-pioneer/build-package-cli@2.1.0
Minor Changes
e4ae880: Switch to
type: modulee4ae880: Implement additional validations when importing modules from other packages.
build-packagewill now check that the imported module actually exists.build-packagenow verifies that the imported module is an actual entry point of that package (declared in thebuild.config.mjs).These validations are designed to errors where a package would run locally (in Vite's development mode) but end up broken when published (see also https://github.com/open-pioneer/trails-core-packages/issues/42).
e4ae880: Introduce an option to configure the root directory (
-rfor the CLI,rootDirectoryfor the JavaScript API).The root directory is used to detect which packages are local to the project. The option defaults to the root of the current workspace (e.g. the PNPM workspace root), or, if that doesn't work, to the root of the current git repository. However, it can also be configured manually.
Patch Changes
@open-pioneer/build-common@2.0.4
Patch Changes
@open-pioneer/vite-plugin-pioneer@3.0.3
Patch Changes