Skip to content

Make emsdk-npm package versions follow EMSDK releases #1

@devappd

Description

@devappd

To follow this versioning scheme, make the NPM releases consistent with EMSDK. (This concerns emsdk-npm only).

  • Implement this by git branching for each EMSDK version. Branches are named v2.0.11, v2.0.10, etc. In each branch, store a default_version.js file that contains the EMSDK version string. This file sets the release to download for the rest of the package. Don't make the version string modifiable by the user. package.json is also edited to reflect the version.
  • Install EMSDK on npm install step when version is hardcoded
  • Make a CI runner to:
    • Mergemain changes to each version branch
    • Publish updated version branches
  • Make a CI runner to:
  • Investigate whether NPM recognizes +build version syntax and ranges them correctly. The +build part will track each main code merge. (e.g. v2.0.11+1609425262 represents the main revision dated 12/31/2020 that serves EMSDK 2.0.11)
  • Track separate NPM packages for the following scenarios:
    • emscripten-sdk: Versioned packages in llvm backend, e.g., emscripten-sdk@2.0.11, emscripten-sdk@2.0.10, etc.
    • emscripten-sdk-npm: Generic package for full control: e.g., requesting latest, fastcomp, tot

Versioning syntax

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions