Adjust npm subpackage namespacing, try getting arm64 working

Author: supermario

extra/npm/bin/lamdera

@@ -15,7 +15,7 @@ module.exports = function()
 	// figure out package of binary
 	// turn '0.19.1-1.2.3-alpha' into '0.19.1-1.2.3'
 	var version = package.version.replace(/^(\d+\.\d+\.\d+)-(\d+\.\d+\.\d+).*$/, '$1');
-	var subPackageName = 'lamdera-' + process.platform + '-' + process.arch;
+	var subPackageName = '@lamdera/compiler-' + process.platform + '-' + process.arch;
 
 	verifyPlatform(version, subPackageName);
 
@@ -75,7 +75,7 @@ function verifyPlatform(version, subPackageName)
 {
 	if (subPackageName in package.optionalDependencies) return;
 
-	var situation = process.platform + '_' + process.arch;
+	var situation = process.platform + '-' + process.arch;
 	console.error(
 		'-- ERROR -----------------------------------------------------------------------\n\n'
 		+ 'The lamdera npm package does not support your platform (' + situation + ').\n\n'

extra/npm/binary.js

@@ -1,6 +1,6 @@
 {
     "name": "lamdera",
-    "version": "0.19.1-1.1.1",
+    "version": "0.19.1-1.1.1-2",
     "description": "npm install wrapper for Lamdera",
     "license": "BSD-3-Clause",
     "repository": "lamdera/compiler",
@@ -28,11 +28,11 @@
         "lamdera": "bin/lamdera"
     },
     "optionalDependencies": {
-        "lamdera-darwin-arm64": "0.19.1-1.1.1",
-        "lamdera-darwin-x64": "0.19.1-1.1.1",
-        "lamdera-linux-arm": "0.19.1-1.1.1",
-        "lamdera-linux-arm64": "0.19.1-1.1.1",
-        "lamdera-linux-x64": "0.19.1-1.1.1",
-        "lamdera-win32-x64": "0.19.1-1.1.1"
+        "@lamdera/compiler-darwin-arm64": "0.19.1-1.1.1",
+        "@lamdera/compiler-darwin-x64": "0.19.1-1.1.1",
+        "@lamdera/compiler-linux-arm": "0.19.1-1.1.1",
+        "@lamdera/compiler-linux-arm64": "0.19.1-1.1.1",
+        "@lamdera/compiler-linux-x64": "0.19.1-1.1.1",
+        "@lamdera/compiler-win32-x64": "0.19.1-1.1.1"
     }
 }

extra/npm/package.json

@@ -0,0 +1,3 @@
+# Lamdera
+
+This is the macOS ARM 64-bit binary for [Lamdera](https://lamdera.com).

extra/npm/packages/lamdera-darwin-arm64/README.md

@@ -0,0 +1,13 @@
+{
+  "name": "@lamdera/compiler-darwin-arm64",
+  "version": "0.19.1-1.1.1",
+  "description": "The macOS ARM 64-bit binary for Lamdera.",
+  "repository": "lamdera/compiler",
+  "license": "BSD-3-Clause",
+  "os": [
+    "darwin"
+  ],
+  "cpu": [
+    "arm64"
+  ]
+}

extra/npm/packages/lamdera-darwin-arm64/package.json

@@ -19,11 +19,11 @@ Create each of these by running the `lamdera` executable for each platform throu
 
 Put the above files at:
 
-1. `packages/lamdera_darwin_arm64/lamdera`
-2. `packages/lamdera_darwin_x64/lamdera`
-3. `packages/lamdera_linux_x64/lamdera`
-4. `packages/lamdera_linux_arm64/lamdera`
-5. `packages/lamdera_win32_x64/lamdera.exe` (Note the `.exe` file extension!)
+1. `packages/lamdera-darwin-arm64/lamdera`
+2. `packages/lamdera-darwin-x64/lamdera`
+3. `packages/lamdera-linux-x64/lamdera`
+4. `packages/lamdera-linux-arm64/lamdera`
+5. `packages/lamdera-win32-x64/lamdera.exe` (Note the `.exe` file extension!)
 
 (They are ignored by git.)
 

extra/npm/publishing.md

@@ -37,7 +37,7 @@ You could also use this package to use different versions of Lamdera in differen
 This works, but there are usually faster and more reliable options:
 
 1. You can download `lamdera` directly from [the downloads page](https://dashboard.lamdera.app/docs/download). This is all the `npm` installer does, but with extra HTTP requests to `npmjs.com` servers, making it slower and adding more failure points.
-2. Many continuous integration pipelines ways to cache files ([example](https://docs.travis-ci.com/user/caching/)) to make builds faster and more reliable.
+2. Many continuous integration pipelines offer ways to cache files ([i.e. github actions cache](https://github.com/marketplace/actions/cache)) to make builds faster and more reliable.
 
 That said, it will definitely work to use the `npm` installer on CI if you prefer that option.