bare-importmaps

To replace node:* imports for Bare runtime compatibility, change specifiers like node:fs to plain builtins such as fs, path, or crypto, and update the nearest package.json import map to ensure the project builds correctly.

Package-local import maps are mappings defined in a project's package.json that route bare specifiers to builtins or polyfills. You need them for Pear or Holepunch projects to ensure dual-runtime JavaScript compatibility across both Node and Bare environments.

No, you should avoid node:* specifiers in code running under the Bare runtime. Bare, Pear, and Holepunch environments require plain builtin specifiers like fs, http, and url to properly resolve modules via package-local import maps.

To update package.json imports when introducing a new builtin, add the plain specifier mapping to the nearest package.json imports field. This ensures the new builtin resolves correctly under Bare while maintaining build safety across dual-runtime environments.

The best way to enforce bare imports is to replace all node:* specifiers with plain builtins like fs or crypto and maintain package-local import maps in the nearest package.json. This ensures consistent resolution and build safety across dual-runtime JavaScript projects.

Your build fails because the nearest package.json import map lacks the mapping for the newly introduced builtin. Update the package.json imports field with the plain specifier to ensure the Bare or Autobonk project resolves the module and builds successfully.