Skip to content

wasm-pack profile name doesn't match the cargo profile name #1488

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
srussvoll opened this issue Apr 2, 2025 · 0 comments · May be fixed by #1489
Open

wasm-pack profile name doesn't match the cargo profile name #1488

srussvoll opened this issue Apr 2, 2025 · 0 comments · May be fixed by #1489

Comments

@srussvoll
Copy link

🐛 Bug description

When running wasm-pack with a custom profile (wasm-pack build . --profile custom_profile_name), the cargo profile with name custom_profile_name will be used, but wasm-pack will use a profile called custom.

More concisely,
Cargo will use [profile.custom_profile_name], whereas
wasm-pack will use [package.metadata.wasm-pack.profile.custom]

🤔 Expected Behavior

wasm-pack should have used [package.metadata.wasm-pack.profile.custom_profile_name].

🌍 Your environment

Include the relevant details of your environment.
wasm-pack version: git revision 32e52ca
@srussvoll srussvoll linked a pull request Apr 2, 2025 that will close this issue
Open
3 tasks
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.

Use the same profile name for both Cargo and wasm-pack Argeo-Robotics/wasm-pack
1 participant
@srussvoll