@epilot/zenith-react 0.1.0-next.0

package/tokens.js

@@ -0,0 +1,13 @@
+// Resolution stub for the `./tokens` subpath.
+//
+// `exports` in package.json already maps it, and webpack, Vite and Node all honour that. Tools
+// that predate `exports` resolve a subpath as a file path instead — `<package>/tokens` becomes
+// `<package>/tokens.js` — and find nothing. ESLint's node import resolver is one of them, so
+// `import/no-unresolved` fires on a specifier that every bundler resolves correctly, and each
+// consumer ends up carrying its own `eslint-disable`.
+//
+// This file is that path. It re-exports the same module the `exports` map points at, so both
+// resolution routes land on one module instance and nothing is duplicated.
+//
+// Same shape as the `typesVersions` entry, which exists for the same reason on the TypeScript side.
+export * from "./dist/tokens/index.js"