Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

`nexe index.js` error "FuseBox failed to initialize."

See original GitHub issue

Is this a BUG or a FEATURE REQUEST?: Bug

What happened:
On a fresh debian install with node v10.15.1,
When launching the command nexe index.js, I get the following message :

$ nexe index.js
ℹ nexe 2.0.0-rc.34

  FuseBox failed to initialize. Please check that:
      - the TypeScript version installed is >= 3.0

What you expected to happen: To build a simple exe file.

How to reproduce it (as minimally and precisely as possible):

Install Debian Stretch 9.7
Install Node 10 via nodesources
Create a simple node script index.js : console.log('Hello World')
Install nexe globally : npm install -g nexe
Start the command : nexe index.js

Anything else we need to know?:
It’s a fresh install of debian so I may not have many common packages.

Environment

Platform(OS/Version): Debian 9.7
Host Node Version: 10.15.1
Target Node Version: 6.4.1
Nexe version: 2.0.0-rc.34
Python Version: none

Issue Analytics

State:
Created 5 years ago
Reactions:4
Comments:13 (2 by maintainers)

Top GitHub Comments

8reactions

fsteffcommented, Feb 21, 2019

Does installing and using nexe@next solve your issue?

I did have this problem too, using nexe@next works perfectly.

7reactions

tamasszarkacommented, Feb 6, 2019

We ran into the same issue last night. The problem is the package.json specifies ^3.1.0 for the version of fuse-box, while they released 3.7.0 yesterday, which explicitly requires typescript 3.0.0< while nexe needs typescript 2.5.3. My workaround was to force installing fuse-box 3.1.0 instead of ^3.1.0.