References in Nuxt setup

[daniilsapa]

Resolves #94

@illright
The cause of the issue was not exactly in the Nuxt setup. The problem was that compilerOption.paths specified in config extensions ("extends": "./.nuxt/tsconfig.json") were not resolved and thus path aliases like @/, ~/ didn't work.

So such paths from extensions were applied to the FSD root.

 {
     "~": [
        ".."
      ],
      "~/*": [
        "../*"
      ],
      "@": [
        ".."
      ],
      "@/*": [
        "../*"
      ],
}

I made changes to transform such paths from ../* to /* and then apply them to the root.

Nuxt setup extends a default config from the .nuxt folder it helped us to uncover this issue.

Sorry for the delay!

[illright]

Could you also resolve the conflicts? Recently there's been a change to that file which did a similar thing, I wonder if your changes overlap with it or not

[daniilsapa]

Got it, yes, let me resolve the conflicts first. Then I'll fix the function and also now I see some other flaws of my solution

[daniilsapa]

@illright

I fixed the first issue that we discussed in the morning by always transforming compilerOptions.paths to absolute, so now we don't have to worry about losing context when running Steiger from a folder other than the one where the original tsconfig is placed.

Regarding the 2nd problem

https://stackblitz.com/edit/nuxt-starter-ap1c4y?file=README.md

How to reproduce

When /src/features/session/logout/index has .js extension. It reports this diagnostic, from which we can see that the file is noticed by the tool.

When /src/features/session/logout/index has .vue extension. It reports the following diagnostic, from which we can see that the tool does not see that the file is imported in other files.

Don't forget to wrap/unwrap the code inside /src/features/session/logout/index with <script></script> when changing extensions

You can temporarily change fileExists, directoryExists parameters from these:

to these (I made that change locally for insignificant-slice)

Then you'll be able to see how it goes through different possible options (like .../logout.ts, .../logout.js, .../logout/index.ts, .../logout/index.js, etc) and then fails when runs out of further options

[daniilsapa]

resolveDependency from .../steiger-plugin-fsd/src/_lib/resolve-dependency.ts uses resolveImport from @feature-sliced/filesystem. It looks like we need to add some wrapper in resolveImport to add .vue extension case. Also, maybe we need to create space to gracefully add more custom extensions, but I'm not sure it's inside the score of the task, we can create a quick fix and an issue to design and implement a module responsible for custom extensions