@eslint/config-inspector@1.5.0 emits root importmap entry (/_nuxt/...) ignoring --base on static build

[Nick2bad4u]

Summary

When building with @eslint/config-inspector@1.5.0 for GitHub Pages project-subpath hosting, the generated HTML includes an importmap entry using root /_nuxt/..., which ignores --base and breaks runtime chunk loading.

1.4.2 with identical command works.

Repro command

npx -y @eslint/config-inspector@1.5.0 build \
  --outDir temp/inspector-1.5.0 \
  --base "/eslint-plugin-typefest/eslint-inspector/"

Expected

All runtime entry/chunk paths should respect --base, e.g.

/eslint-plugin-typefest/eslint-inspector/_nuxt/...

Actual (1.5.0 output)

Generated index.html includes:

<script type="importmap">{"imports":{"#entry":"/_nuxt/T86v09Lr.js"}}</script>

This causes browser requests to:

https://<host>/_nuxt/...

instead of subpath:

https://<host>/<repo>/eslint-inspector/_nuxt/...

Result: dynamic import failures / 404s on project-subpath deployments.

Comparison with 1.4.2

Using the same command with @eslint/config-inspector@1.4.2 works and does not emit this root importmap entry.

I built both versions with the same flags:

npx -y @eslint/config-inspector@1.4.2 build --outDir temp/inspector-ab-.../v1.4.2 --base "/eslint-plugin-typefest/eslint-inspector/"
npx -y @eslint/config-inspector@1.5.0 build --outDir temp/inspector-ab-.../v1.5.0 --base "/eslint-plugin-typefest/eslint-inspector/"

Both exited 0, both produced index.html.

Key difference in emitted HTML
1.4.2: no importmap entry forcing root /_nuxt entry.
1.5.0: emits:

<script type="importmap">{"imports":{"#entry":"/_nuxt/T86v09Lr.js"}}</script>
That absolute /_nuxt/... ignores your repo subpath and causes requests to:
https://nick2bad4u.github.io/_nuxt/...

instead of: https://nick2bad4u.github.io/eslint-plugin-typefest/eslint-inspector/_nuxt/...

Environment

• Hosting: GitHub Pages deployment
• Docusaurus site (all my docusaurus sites are affected when linking to eslint-config-inspector)

[snitin315]

Hi @Nick2bad4u, can you please share a GitHub repo where we can see the issue in action? Maybe a PR where you tried upgrading and the CI failed.

[Nick2bad4u]

Hi @Nick2bad4u, can you please share a GitHub repo where we can see the issue in action? Maybe a PR where you tried upgrading and the CI failed.

are you saying you aren't getting this issue in the repro above? it should be the same in any repo or setting that uses the new version to output a static build to a non-root dir.

This is how you can fix it: as I did in my fork for stylelint config inspector based off this repo:

Nick2bad4u@22c21c8

const RE_ABSOLUTE_ASSET_ATTR = /\s(href|src)="\//g
const RE_IMPORTMAP_ENTRY = /("#entry"\s*:\s*")\/_nuxt\//g

export function rewriteStaticHtmlWithBase(content: string, baseURL: string): string {
  if (baseURL === '/')
    return content

  return content
    .replaceAll(RE_ABSOLUTE_ASSET_ATTR, ` $1="${baseURL}`)
    .replaceAll('baseURL:"/"', `baseURL:"${baseURL}"`)
    .replaceAll(RE_IMPORTMAP_ENTRY, `$1${baseURL}_nuxt/`)
}

If you want I can build the static site with the new version and host it so you can see the devtools errors in the browser if needed.