vcbuild.bat nosign release x64 exited with code: 1
See original GitHub issueWhat happened: I’m trying to build a version of my node js project, but always get this error:
nexe 3.3.7
√ Downloading Node.jssource from: https://nodejs.org/dist/v12.16.3/node-v12.16.3.tar.gz
√ Already downloaded...
√ Compiling result
√ Configuring node build...
Compiling Node with arguments: nosign,release,x64
Note: vcbuild no longer signs by default. "nosign" is redundant.
Looking for Python
Python 2 found in C:\Python27\\python.exe
Looking for NASM
Looking for Visual Studio 2017
Failed to find a suitable Visual Studio installation.
Try to run in a "Developer Command Prompt" or consult
https://github.com/nodejs/node/blob/master/BUILDING.md#windows-1
√ Compiling Node with arguments: nosign,release,x64
√ Finished in 8.422s
(node:5552) UnhandledPromiseRejectionWarning: Error: vcbuild.bat nosign release x64 exited with code: 1
at new NexeError (C:\Users\dpapi\Documents\bot raffle\black rabbit\node_modules\nexe\lib\compiler.js:83:28)
at ChildProcess.<anonymous> (C:\Users\dpapi\Documents\bot raffle\black rabbit\node_modules\nexe\lib\compiler.js:274:28)
at Object.onceWrapper (events.js:417:26)
at ChildProcess.emit (events.js:310:20)
at maybeClose (internal/child_process.js:1021:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
(node:5552) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:5552) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
What you expected to happen: Build the application
How to reproduce it (as minimally and precisely as possible): Create a file and enter this code:
const { compile } = require('nexe')
compile({
input: './index.js',
build: true, //required to use patches
ico: './favicon.ico',
verbose: true
}).then(() => {
console.log('success')
})
Environment:
- Platform(OS/Version):
- Host Node Version: 12.16.3
- Target Node Version: 12.16.3
- Nexe version: 3.3.7
- Python Version: 3.8.5
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:30 (3 by maintainers)
Top Results From Across the Web
I have a problem with npm package nexe and visual studio ...
the message said: failed to find a suitable Visual studio installation and also vcbuild.bat nosign release x64 exited with code: 1 ...
Read more >nexe Error: vcbuild.bat nosign release x64 exited with code: 1
1 - run this: npx nexe server.js -o test -t windows --build --verbose // 2 - if you have this message in console:...
Read more >Windows Build | IfxNode - GitHub Pages
Say you have extracted NodeJS sourct at **C:\work\node-v10.15.1** cd C:\work\node-v10.15.1 SET NODE_SRC=C:\work\node-v10.15.1 vcbuild.bat nosign release x64 ...
Read more >vcbuild.bat - Google Git
if errorlevel 1 echo Failed to generate license.rtf&goto exit ... echo vcbuild.bat release msi : builds release build and MSI installer package.
Read more >Process Exited With Code 1 Command Prompt Error on ...
Process Exited With Code 1 Command Prompt Error on Windows 10/11 FIXPowerShell Command Used: C:\Windows\System32\reg.exe DELETE ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I have run the command
nexe index.js -o test -t windows --buildagain with parameter--verbose. The output shows, that NASM is required and not installed. After installing NASM manually from here it works like a charm!You will need to install NASM manually here, after installing it, it worked without any errors!