Simon Hänisch

k not sure this is a use case that can be supported, not even sure how it's supposed to work without a path alias. are you using some custom loader...

Ok cool I wasn't aware that Rollup has released a v3 yet (not actively working with Rollup anymore at the moment). https://rollupjs.org/migration/#changes-to-the-plugin-api looks like there were some plugin API changes...

Sorry @elado just read your message properly... can you maybe try a patch in your project by opening `node_modules/rollup-plugin-typescript-paths/dist/index.js`, and in line 19 at the end change ```js outDir =...

What I wonder is why you'd get an absolute path in the first place... usually import paths are always relative?

Just from having a quick look at this again, it seems like using `path.join` here https://github.com/simonhaenisch/rollup-plugin-typescript-paths/blob/a65deddb4edb445e47e95e534034a51ef812caeb/index.ts#L49-L52 is ~incorrect~ not always correct? it should instead use `path.relative` or sth to find...

Ok cool, thanks for testing that! Just to confirm, you just switched out `join` with `relative` and that did the trick?

I was under the assumption that `baseUrl` is required to use `paths` but seems like that changed at some point after this plugin was published, see https://github.com/microsoft/TypeScript/issues/31869. I haven't worked...

> I was surprised that the plugin code is so convoluted Not sure what you mean, the actual implementation is less than 60 lines of code? 🤷🏻‍♂️ > tested with...

Also happens with custom web components when nested, e. g. 

I haven't used Astro yet, but since it's similar to Vue or Svelte wrt the `.astro` file structure, I think Volar could provide the base tooling for it (not working...