Skip to content

fix: correct Windows path resolution in parser init#892

Merged
jtkiesel merged 3 commits into
jhipster:mainfrom
ralscha:fix/windows-path
May 18, 2026
Merged

fix: correct Windows path resolution in parser init#892
jtkiesel merged 3 commits into
jhipster:mainfrom
ralscha:fix/windows-path

Conversation

@ralscha
Copy link
Copy Markdown
Contributor

@ralscha ralscha commented May 18, 2026

What changed with this PR:

Fix the invalid path on Windows when loading the treesitter wasm file

Example

 no such file or directory, open 'C:\C:\.....\target\spotless-prettier-node-modules-a419b185f88f4c8243af8729ce04d5c8\node_modules\prettier-plugin-java\dist\tree-sitter-java_orchard.wasm'

@DanielFran DanielFran requested a review from jtkiesel May 18, 2026 13:15
@jtkiesel
Copy link
Copy Markdown
Contributor

Thanks for the contribution (and inherently reporting this issue)! Unfortunately, this breaks use of this plugin in web (as can be seen by the failed GitHub Pages CI job). We purposefully omitted use of Node.js-only libraries for this reason. I will see if there's another way we can resolve this issue.

Comment thread src/parser.ts Outdated
Comment thread src/parser.ts Outdated
@jtkiesel jtkiesel changed the title fix invalid path on windows: C:\C:\....wasm fix: correct Windows path resolution in parser init May 18, 2026
@jtkiesel jtkiesel merged commit 8c63a28 into jhipster:main May 18, 2026
6 checks passed
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