turbo-windows-64 0.9.0-next.0

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/README.md ADDED
@@ -0,0 +1,3 @@
1
+ # turbo
2
+
3
+ This is the Windows 64-bit binary for turbo, a monorepo build system. See https://github.com/turborepo/turbo for details.
package/bin/turbo ADDED
@@ -0,0 +1,14 @@
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 turbo_exe = require.resolve('turbo-windows-64/turbo.exe');
13
+ const child_process = require('child_process');
14
+ child_process.spawnSync(turbo_exe, process.argv.slice(2), { stdio: 'inherit' });
package/package.json ADDED
@@ -0,0 +1,16 @@
1
+ {
2
+ "name": "turbo-windows-64",
3
+ "version": "0.9.0-next.0",
4
+ "description": "The Windows 64-bit binary for turbo, a monorepo build system.",
5
+ "repository": "https://github.com/turborepo/turbo",
6
+ "license": "SEE LICENSE IN TRIAL AGREEMENT",
7
+ "os": [
8
+ "win32"
9
+ ],
10
+ "cpu": [
11
+ "x64"
12
+ ],
13
+ "directories": {
14
+ "bin": "bin"
15
+ }
16
+ }
package/turbo.exe ADDED
Binary file