v0.2.1

Patch Changes

• #8 113bdb8 Thanks @sapphi-red! - Derive the tracking query name from a per-instance random value (fresh-import-<instance>). Previously two copies of the same build loaded into one process (e.g. Vite bundles fresh-import while another package uses a separately bundled copy) registered the same query name, so only the first-registered hook captured the imports. A random value unique to each loaded module instance keeps their hooks distinct. This replaces the build-time hash, which could not disambiguate two instances of the same build.

v0.2.0

Minor Changes

• #6 a19d7d9 Thanks @sapphi-red! - Replace createFreshImporter with a freshImport(specifier) function and remove the queryName option.

  • freshImport(specifier) imports an entry in a fresh module graph and resolves to { result, dependencies }. It lazily creates and reuses a single underlying importer (registering the resolution hook once) instead of one per call. On runtimes that provide neither Module.registerHooks nor Module.register (e.g. non-Node), it returns undefined, mirroring createFreshImporter's old undefined return.
  • The tracking query name is now derived internally as fresh-import-<hash> (a build-time hash of the output), so the queryName option and the FreshImporterOptions type are gone.

  -import { createFreshImporter } from 'fresh-import'
  -const importer = createFreshImporter()
  -const { result, dependencies } = await importer.collect(url)
  +import { freshImport } from 'fresh-import'
  +const { result, dependencies } = await freshImport(url)

v0.1.0

Minor Changes

• #4 db48f43 Thanks @sapphi-red! - Simplify interface by running the dynamic import internally.

Patch Changes

• e21d32b Thanks @sapphi-red! - use t as the default value of queryName option

v0.0.2

Patch Changes

• 1647ecc: setup trusted publishing