Skip to content
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.

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

Don't exclude the no-modules target from NPM builds #81

Merged
merged 5 commits into from
Nov 20, 2020

Conversation

cormacrelf
Copy link
Collaborator

@cormacrelf cormacrelf commented Nov 20, 2020

The no-modules build wasn't listed in the package.json's files manifest, so it never got published. That was a bit of an oversight. Now you should be able to use it as described in the README.

It also includes some debug info in the published releases, so any stack traces from any panics that occur aren't nonsense, which previously I hadn't been able to get through wasm-opt.

  • Preserve debug info through wasm-opt
  • Remove &mut self from wasm Driver methods so it survives a panic
  • Include _no_modules output to NPM package
  • Set some better durabilities so salsa can optimize validation

...without saying 'recursive use of an object detected ... that would
lead to unsafe aliasing in rust' due to wasm-bindgen runtime checks.
For whatever reason the runtime isn't releasing its Rc lock on Driver,
but this change is fine since we already have an Rc over the engine.
The npmrc has a precedence list, so >> was incorrect.
@cormacrelf cormacrelf merged commit ce08631 into master Nov 20, 2020
@cormacrelf cormacrelf added A-wasm Area: wasm package on npm I-packaging Issue: problem with a built package labels Sep 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-wasm Area: wasm package on npm I-packaging Issue: problem with a built package
Development

Successfully merging this pull request may close these issues.

None yet

1 participant