Neon packaging #75
Neon packaging #75
Conversation
Removed the native directory. Made the tests run expecting the same structure as what we distribute. That same structure is created by either running `yarn compile` or `node-pre-gyp install` (the second being how and end user gets the binary). The publish structure is the same other than the new entry point, so that should continue working.
skeet70
requested review from
coltfred and
cjyar
and removed request for
a team
|
No changes to code coverage between the base branch and the head branch |
1 similar comment
|
No changes to code coverage between the base branch and the head branch |
|
No changes to code coverage between the base branch and the head branch |
|
I additionally tested this by linking the result after a |
|
No changes to code coverage between the base branch and the head branch |
|
No changes to code coverage between the base branch and the head branch |
1 similar comment
|
No changes to code coverage between the base branch and the head branch |
|
No changes to code coverage between the base branch and the head branch |
|
No changes to code coverage between the base branch and the head branch |
Should still dodge the weird GH issue tracked by jestjs/jest#10662 but won't impact local machine runs as much
|
No changes to code coverage between the base branch and the head branch |
* Update to latest of all deps * Recrypt 0.12 * Try Node 16 as well * Reduce cardinality * Bump MSRV to 1.51 * Update documentation. * Upgrade JS dependencies too. * Replace Node 10 with 16 in the matrix * Apply patch * Update recrypt * And changelog * Rust 2021 so we can use recrypt 0.13 * Checkpointing migration to NAPI * Try different coverage switch command * Rust fmt * Neon packaging (#75) Removed the native directory. Made the tests run expecting the same structure as what we distribute. That same structure is created by either running `yarn compile` or `node-pre-gyp install` (the second being how and end user gets the binary). The publish structure is the same other than the new entry point, so that should continue working. * Add NAPI to changelog, would be good to remember * bump-version: Set release version 0.8.0-pre.1 * Add a comment to clarify where changes happen Limited jest `maxWorkers` to dodge the weird GH issue tracked by jestjs/jest#10662 but won't impact local machine runs as much Co-authored-by: Leeroy Travis <ops@ironcorelabs.com> Co-authored-by: Murph Murphy <murph@clurictec.com> Co-authored-by: Leeroy Travis <ops@ironcorelabs.com>
Moves to the new neon build process, removes now dead dependencies and publish steps. Makes sure that what we test is as close as possible to what gets distributed.