💡 Nuxt 4 Support

[OrbisK]

Suggest an idea for Knip

It looks like nuxt 4 paths are not yet supported.

@danielroe I wonder if we could integrate with Knip more effectively by creating a nuxt module/knip plugin that generates the correct Knip configuration with nuxts context 🤔

[danielroe]

Indeed, I think we should have a Nuxt plugin, and this should be relatively straightforward.

[webpro]

What are nuxt 4 paths?

If it is what I think it is, Knip plugins can return TS config style path aliases (example), though this is still undocumented I see.

Knip has a Nuxt plugin (source), it's just not very advanced.

[OrbisK]

@webpro I experimented a bit.

I resolved the relevant paths with nuxt/kit: https://github.com/OrbisK/knip/blob/feat/nuxt/packages/knip/src/plugins/nuxt/index.ts (prototype)

However, this approach only resolves the static nuxt config.

[OrbisK]

Do you think knip will support extending configs/patterns from a path in the near future?

This would allow us to write a Nuxt module to generate a .nuxt/knip.json file containing all entry points and dependencies within the nuxt context (on nuxt prepare). It would work in a similar way to nuxt/eslints approach: https://eslint.nuxt.com/packages/module#manual-setup

// knip.json
{
  extends: [
    ".nuxt/knip.json"
  ]
}

This should eliminate false positive and false negative issues with layers, local modules and custom configuration patterns.

[webpro]

Maybe we could get away by adding e.g. .nuxt/knip.json to the config array? Would require a "hybrid" resolveConfig so that it handles both files separately but in a single function (not pretty, but more plugins do this e.g. example). not sure if feasible in this case though.

Btw why would we need @nuxt/kit?

[OrbisK]

Maybe we could get away by adding e.g. .nuxt/knip.json to the config array? Would require a "hybrid" resolveConfig so that it handles both files separately but in a single function (not pretty, but more plugins do this e.g. example). not sure if feasible in this case though.

I think if we detect a .nuxt/knip.json, we dont want to apply the default config.

Btw why would we need @nuxt/kit?

@nuxt/kit should always have the correct default values when resolving the config.