feat: Throw a better error message when using wrong imports

[mrousavy]

When doing this:

import { SomeType } from '@src/SomeType'

Nitrogen might not know where to import SomeType from because @src is a path alias created from the user's tsconfig.json.

Nitrogen does not use the user's tsconfig.json though, so it has to be imported like this instead:

import { SomeType } from '../SomeType'

This will work.

This PR now throws a better error message in these situations:

- The TypeScript type "SomeType" cannot be represented in C++!
+ The TypeScript type "SomeType" cannot be resolved - is it imported properly? Make sure to import it properly using fully specified relative or absolute imports, no aliases.

• Closes TS/JS module path aliases don't work #457

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
nitro-docs	⬜️ Skipped (Inspect)			Jan 8, 2025 10:39am