Open source / Nuxt module

layerscope.

Layer boundaries that see auto-imports.

The layerscope tab in Nuxt DevTools. A graph of five layers with two violating edges, and a list of files with findings.
The DevTools tab draws the layer graph and marks each edge that breaks a rule. It updates when you save a file.

In a Nuxt app, a component in one layer can call a composable from another layer with no import statement. layerscope resolves auto-imports the same way Nuxt does and fails CI when a layer uses something it is not allowed to.

What import-based tools miss

Composables, components, Nitro server utils and regular imports all go through one resolver. The check covers the app, server and shared directories, and local, npm and remote layers on Nuxt 3 and 4.

Made for existing projects

init writes a starter config, and every finding comes with a suggested fix. A baseline accepts the violations you already have, and a drift report shows what each pull request adds and removes.

In CI and in the editor

Use the CLI with why, graph and unused, the GitHub Action, or the ESLint plugin. The Nuxt DevTools tab shows the layer graph and every finding, and updates when you save a file.

← All projects Back to projects