lefthook-windows-arm64 0.0.3 → 1.0.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/bin/lefthook.exe +0 -0
- package/package.json +1 -4
- package/bin/lefthook +0 -14
package/bin/lefthook.exe
CHANGED
|
Binary file
|
package/package.json
CHANGED
|
@@ -1,10 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "lefthook-windows-arm64",
|
|
3
|
-
"version": "
|
|
3
|
+
"version": "1.0.2",
|
|
4
4
|
"description": "The Windows ARM 64-bit binary for lefthook, git hooks manager.",
|
|
5
|
-
"bin": {
|
|
6
|
-
"lefthook": "bin/lefthook.exe"
|
|
7
|
-
},
|
|
8
5
|
"preferUnplugged": false,
|
|
9
6
|
"repository": "https://github.com/evilmartians/lefthook",
|
|
10
7
|
"license": "MIT",
|
package/bin/lefthook
DELETED
|
@@ -1,14 +0,0 @@
|
|
|
1
|
-
#!/usr/bin/env node
|
|
2
|
-
|
|
3
|
-
// Unfortunately even though npm shims "bin" commands on Windows with auto-
|
|
4
|
-
// generated forwarding scripts, it doesn't strip the ".exe" from the file name
|
|
5
|
-
// first. So it's possible to publish executables via npm on all platforms
|
|
6
|
-
// except Windows. I consider this a npm bug.
|
|
7
|
-
//
|
|
8
|
-
// My workaround is to add this script as another layer of indirection. It'll
|
|
9
|
-
// be slower because node has to boot up just to shell out to the actual exe,
|
|
10
|
-
// but Windows is somewhat of a second-class platform to npm so it's the best
|
|
11
|
-
// I can do I think.
|
|
12
|
-
const esbuild_exe = require.resolve('lefthook-windows-arm64/bin/lefthook.exe');
|
|
13
|
-
const child_process = require('child_process');
|
|
14
|
-
child_process.spawnSync(esbuild_exe, process.argv.slice(2), { stdio: 'inherit' });
|