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.

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

Use emscripten-sdk versioned packages #18

Closed
2 tasks done
devappd opened this issue Jan 11, 2021 · 2 comments
Closed
2 tasks done

Use emscripten-sdk versioned packages #18

devappd opened this issue Jan 11, 2021 · 2 comments
Milestone
1.0.0

Comments

@devappd
Copy link
Owner

devappd commented Jan 11, 2021 •
edited
Loading

With regard to devappd/emscripten-sdk-npm#1, this allows the user to specify their EMSDK by package.json.

  • Research NPM co-dependency install behavior
  • See if there's away to preserve emscripten-sdk-npm compatibility (non-versioned packages)
@devappd devappd added this to the 1.0.0 milestone Jan 11, 2021
@devappd
Copy link
Owner Author

devappd commented Jan 12, 2021

Addressed by 332dd76

@devappd
Copy link
Owner Author

devappd commented Jan 14, 2021

Ruled out because the upgrade experience with versioned packages is awkward.

Due to relying on prerelease digits to denote the build number, the user is limited to forcing one SDK version at a time. They will not receive version upgrades unless they opt-in via npm install -D emscripten-sdk@latest.

To prioritize ease-of-use, I'll continue to use the non-versioned package (emscripten-sdk-npm).

@devappd devappd closed this as completed Jan 14, 2021
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
1.0.0
Development

No branches or pull requests
1 participant
@devappd