@esy-nightly/esy - npm Package Compare versions

Comparing version 0.3.4-de4a6d to 0.4.0-682142

package.json

 {
   "name": "@esy-nightly/esy",
-  "version": "0.3.4-de4a6d",
+  "version": "0.4.0-682142",
   "license": "MIT",
@@ -21,5 +21,5 @@ "description": "Package builder for esy",
     "platform-darwin/",
-    "platform-windows-x64/",
+    "platform-win32/",
     "_build/default/**/*.exe"
   ]
 }

postinstall.js

@@ -27,3 +27,9 @@ /**
   ),
-  path.join('_build', 'default', 'esy-build-package', 'bin', 'fastreplacestring.exe')
+  path.join(
+    '_build',
+    'default',
+    'esy-build-package',
+    'bin',
+    'esyRewritePrefixCommand.exe'
+  )
 ];
@@ -120,5 +126,5 @@
 
-    console.log('Installing cygwin sandbox...');
-    cp.execSync(`npm install esy-bash@0.3.9 --prefix ${__dirname}`);
-    console.log('Cygwin installed successfully.');
+    console.log('Installing native compiler toolchain for Windows...');
+    cp.execSync(`npm install esy-bash@0.3.16 --prefix ${__dirname}`);
+    console.log('Native compiler toolchain installed successfully.');
     break;
@@ -125,0 +131,0 @@ case 'linux':

README.md

@@ -5,6 +5,3 @@ # esy
 
-[![AppVeyor](https://ci.appveyor.com/api/projects/status/0x1mwqeblcgpqyc0/branch/master?svg=true)](https://ci.appveyor.com/project/esy/esy/branch/master)
-[![Travis](https://travis-ci.org/esy/esy.svg?branch=master)](https://travis-ci.org/esy/esy)
-[![npm](https://img.shields.io/npm/v/esy.svg)](https://www.npmjs.com/package/esy)
-[![npm (tag)](https://img.shields.io/npm/v/esy/next.svg)](https://www.npmjs.com/package/esy)
+[![Build Status](https://dev.azure.com/esy-dev/esy/_apis/build/status/build)](https://dev.azure.com/esy-dev/esy/_build/latest?definitionId=1)
 
@@ -154,19 +151,19 @@ This README serves as a development documentation for esy. For user
 Because esy is written in OCaml/Reason and compiled into a native executable we
-need to acquire a set of prebuilt binaries. We employ CI servers (thanks Travis
-CI) to build platform specific releases.
+need to acquire a set of prebuilt binaries for each supported platform (Windows,
+macOS and Linux). We employ CI servers (thanks Azure) to build platform specific
+releases.
 
 The release workflow is the following:
 
-1.  Ensure you arre on `master` branch and run
+1.  Ensure you are on `master` branch and assuming you want to release the
+    version currently defined in `package.json` (see step 6.), run
 
     ```
-    % make bump-patch-verson
+    % make release-tag
     % git push && git push --tags
     ```
 
-    (this bumps patch version, use `bump-minor-version` or `bump-major-version`
-    correspondingly to bump either minor or major version of esy)
+2.  Wait till CI finishes its task and release `@esy-nightly/esy` package.
 
-2.  Wait till CI finishes its task and uploads releases on GitHub,
-    check https://github.com/esy/esy/releases for them.
+    You can test it manually.
 
@@ -176,17 +173,37 @@ 3.  Run
     ```
-    % make release
+    % make release-prepare
     ```
 
-    Which downloads platform specific releases (which CI uploaded GitHub) and
-    produces an npm releases with needed metadata inside `_release` directory.
+    which downloads the nightly corresponding to the current commit working
+    directory is at and "promotes" it to a release. It will create
+    `_release/package` directory.
 
-4.  Ensure release inside `_release` directory is ok.
+4.  Ensure release inside `_release/package` directory is ok.
 
-    You can `cd _release && npm pack && npm install -g ./esy-*.tgz` to test how
+    You can `cd _release/package && npm pack && npm install -g ./esy-*.tgz` to test how
     release installs and feels.
 
-5.  Run `cd _release && npm publish` to publish release on npm.
+5.  Run
 
-    Release tag `next` is used to publish preview releases.
+    ```
+    % make release-publish
+    ```
 
+    to upload the release on npm.
+
+    Use
+
+    ```
+    % make NPM_RELEASE_TAG=next release-publish
+    ```
+
+    To publish release under `next` tag (so users won't get it automatically but
+    only explicitly requested).
+
+6.  Bump version in `package.json` to the next patch version.
+
+    We expect next version to be patch version most of the time. In case you
+    want to release new minor or major version you need to bump it before the
+    reelase.
+
 [hello-ocaml]: https://github.com/esy-ocaml/hello-ocaml
@@ -193,0 +210,0 @@ [hello-reason]: https://github.com/esy-ocaml/hello-reason

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Native code

Supply chain risk

Contains native code (e.g., compiled binaries or shared libraries). Including native code can obscure malicious behavior.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Native code

Supply chain risk

Contains native code (e.g., compiled binaries or shared libraries). Including native code can obscure malicious behavior.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

158954858

increased by119.45%

Number of package files

17

increased by21.43%

Lines of code

495

increased by1.23%

Number of lines in readme file

218

increased by8.46%

Worsened metrics

Number of medium supply chain risk alerts

14

increased by27.27%

No dependency changes