Daniel Costrasel

@slorber I created the [docusaurus-plugin-relative-paths](https://github.com/ohkimur/docusaurus-plugin-relative-paths) to solve the issue. I used the same post-processing approach using Docusaurus `postBuild` lifecycle. 🦖😎

> @roguexz , if you used a modern Jamstack tool like Netlify or Vercel (both much better than GH pages), you'd get a much better experience and all PRs would...

@larissa-n Thank you for your observations. I know about the issue you mentioned, but I didn't fix it since I didn't find an elegant approach to do it. If you...

@jeacott1 Yeah. I did. I want to invest my time into something different.

@qmhc We need a fix for this. It's making life hard when using monorepos. For example, if there is at least one private package that is imported into another public...

@qmhc I've updated the demo with a situation as close to the one I have. Here is a link: https://stackblitz.com/edit/vitejs-vite-k5aekx If you go to `packages/foo/dist` and check `foo.d.ts` you'll see...

@avp1598 Your setup is very similar to mine. I also use `turborepo` and multiple packages that are powered by `vite`. Here is how I setup the `dts` for my packages:...

@pandeymangg Yeah, this is also the case for my monorepo. You can `rollupTypes` as a workaround, but that is far from the correct behavior. @qmhc Do you have any ideas...

Do we have a proper solution for this? We should tell `package` to preprocess all the CSS and include it in the final `dist` folder. @Laaouatni 's answer is far...

@crutchcorn If you would like to fix it, please do it. Let me know if I can help.