Skip to content

Consider making wizer path configurable #222

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
tomasol opened this issue May 5, 2025 · 0 comments · May be fixed by #223
Open

Consider making wizer path configurable #222

tomasol opened this issue May 5, 2025 · 0 comments · May be fixed by #223

Comments

@tomasol
Copy link

tomasol commented May 5, 2025

Similar to opts.wevalBin, I propose adding wizerBin. Running downloaded binaries can cause issues with reproducibility, security, and compatibility - for example, the downloaded binary doesn't work on NixOS.
tomasol added a commit to tomasol/ComponentizeJS that referenced this issue May 10, 2025
@tomasol
Allow customizing wizer path using opts.wizerBin
e31a25a 
Fixes bytecodealliance#222
@tomasol tomasol linked a pull request May 10, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Allow customizing wizer path using opts.wizerBin tomasol/ComponentizeJS
1 participant
@tomasol