Skip to content

Conversation

@nojaf
Copy link
Member

@nojaf nojaf commented Jan 6, 2026

Fixes #8150

It does use the absolute path for now.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Jan 6, 2026

Open in StackBlitz

rescript

npm i https://pkg.pr.new/rescript-lang/rescript@8151

@rescript/darwin-arm64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/darwin-arm64@8151

@rescript/darwin-x64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/darwin-x64@8151

@rescript/linux-arm64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/linux-arm64@8151

@rescript/linux-x64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/linux-x64@8151

@rescript/runtime

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/runtime@8151

@rescript/win32-x64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/win32-x64@8151

commit: ac4efda

@nojaf
Copy link
Member Author

nojaf commented Jan 8, 2026

@cknitt any thoughts on how big of a deal the absolute path is here?

@cknitt
Copy link
Member

cknitt commented Jan 11, 2026

I agree that passing an absolute path should be clearer.
I have never used this feature in practice though.
Maybe ask in the forum post for feedback? https://forum.rescript-lang.org/t/rescript-v12-js-post-build-confusion/7053

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.

Support js-post-build

2 participants