Skip to content

fix(vite-plugin): always resolve typst imports to absolute paths#835

Open
pynappo wants to merge 2 commits intoMyriad-Dreamin:mainfrom
pynappo:fix/relpath-import-issue
Open

fix(vite-plugin): always resolve typst imports to absolute paths#835
pynappo wants to merge 2 commits intoMyriad-Dreamin:mainfrom
pynappo:fix/relpath-import-issue

Conversation

@pynappo
Copy link

@pynappo pynappo commented Feb 26, 2026

I don't know if this is the correct fix but it does work for me, i just came up with the fix after debugging for a while and looked at various vite plugins to see if they do similar things.

Motivation: I'm setting up a SvelteKit blog and I want to write articles in typst then compile to HTML.

Expected:

When i have this /blog/article/[[slug]]/page.server.ts, navigating to /blog/article/init should be able to properly import blog/article/init.typ.

Actual:

Somehow, this works with vite dev but not vite build. It looks like when I use a relative path to a typst file, the vite plugin does not resolve the relative id, so the compiler assumes the path is relative to the root of the project at build time.

In dev, it seems like vite automatically resolves the id to an absolute path before the vite plugin gets it.

I originally figured out this behavior by switching the vite plugin to use typst-cli and then printing out the command that vite-plugin-typst uses. I don't have the exact logs atm but it was basically:

With vite dev:

typst compile --root /root/of/project/typst /root/of/project/typst/src/routes/blog/article/init.typ

With vite build:

typst compile --root /root/of/project/typst ../init.typ

@Myriad-Dreamin
Copy link
Owner

I don't know if we will solve the issue but these changes generally look good to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants