Skip to content

Using nexe@beta on Manjaro Linux errors on checking compiled node binary #354

@reinaldorauch

Description

@reinaldorauch

This is a

  • Bug Report
  • Feature Request
  • Other

Steps to reproduce:

  • Create a folder, initialize it with npm init and use default settings.
  • Create a index.js file with this content:
    console.log("Hello World");
    
  • Install nexe@beta in project with npm i -D nexe@beta
  • Run npx nexe -i index.js -o index
  • Output would be:
✔ Using input file as the main module: index.js
✔ Node source extracted to: /home/reinaldoacr/projetos/nexe-test/.nexe/8.1.4
✔ Node binary compiled
⠋ Writing result to fileevents.js:182
      throw er; // Unhandled 'error' event
      ^

Error: ENOENT: no such file or directory, open '/home/reinaldoacr/projetos/nexe-test/.nexe/8.1.4/out/Release/node'




Please also provide:

  • Platform(OS/Version):
lsb_release -a
LSB Version:	n/a
Distributor ID:	ManjaroLinux
Description:	Manjaro Linux
Release:	17.0.2
Codename:	Gellivara
uname -a
Linux reinaldo-note-manjaro 4.9.38-1-MANJARO #1 SMP PREEMPT Sat Jul 15 12:04:06 UTC 2017 x86_64 GNU/Linux
  • Host Node Version: v8.1.4
  • Target Node Version: v8.1.4
  • Nexe version: 2.0.0-beta.2
  • Python Version: python 3.6.1, python2 2.7.13

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions