Skip to content
This repository has been archived by the owner on Jan 13, 2024. It is now read-only.

No available node version satisfies 'node13' #838

Closed
cylexVEVO opened this issue Jan 31, 2020 · 18 comments
Closed

No available node version satisfies 'node13' #838

cylexVEVO opened this issue Jan 31, 2020 · 18 comments

Comments

@cylexVEVO
Copy link

When I run pkg [file] --targets node13-win-x86 it gives me the error

> pkg@4.4.2
> Error! No available node version satisfies 'node13'

However, when I run node -v it outputs with v13.5.0.

I'm using Windows 10 build 1909.

@deepseapenguin
Copy link

deepseapenguin commented Feb 7, 2020

same issue here

 node -v
v13.6.0

@asmello
Copy link

asmello commented Feb 23, 2020

Same here, but for Mac OS (node installed via homebrew):

> node -v
v13.8.0
> pkg -v
4.4.3
> sw_vers -productVersion
10.15.3

BTW can confirm that choosing node12-macos-x64 or latest-macos-x64 as targets does work.

@LeeJaeWonLJW
Copy link

Same issue for me.

 ▓▒░ node -v
v13.8.0

▓▒░ pkg -v
4.4.3

@weiying-chen
Copy link

weiying-chen commented Feb 26, 2020

Same issue here.

> pkg@4.4.3
> Targets not specified. Assuming:
  node13-linux-x64, node13-macos-x64, node13-win-x64
> Error! No available node version satisfies 'node13'

I'm using Node v13.7.0.

@patrolez
Copy link

patrolez commented Feb 26, 2020

This is related to sub-project https://github.com/zeit/pkg-fetch which have to poses corresponding definitions and patches for specific nodejs versions.

Contributions are needed in pkg-fetch.

Another issue which confirms pkg architecture:
#331 (comment)

Imho https://github.com/nexe/nexe is less complicated in its architecture and all needed things are in singular GitHub repository, but nexe also needs contributions in a similar matter - related to patching nodejs.

@paulocoghi
Copy link

The problem of zeit/pkg-fetch is that it doesn't have any instructions on how we can contribute to it, helping to release new and updated versions.

@paulocoghi
Copy link

paulocoghi commented Feb 27, 2020

I opened an issue here: https://github.com/zeit/pkg-fetch/issues/78

@hustjiangtao
Copy link

On my mac, use node8 will be help. While node9, node10...node13 doesn't work.
My node version is v13.6.0

$ pkg -t node8-macos index.js
> pkg@4.4.4
> Fetching base Node.js binaries to PKG_CACHE_PATH
  fetched-v8.16.2-macos-x64    [====================] 100%
index    index.js

Hope can help you.

@wis
Copy link

wis commented Mar 14, 2020

use a node version manager like nvm, it looks like the latest version is 12.13.1
so nvm install 12.13.1 then run npm use 12.13.1 before running your builds

@autr
Copy link

autr commented Mar 20, 2020

Bump ^ I am having troubles with ESM, which is fixed in latest 13.11.0

@autr
Copy link

autr commented Mar 20, 2020

@AdamCyber
Copy link

here's what i did (mac):
$ npm install -g n
$ n 13.0
$ pkg .

@robertsLando
Copy link
Contributor

Maybe this can help: https://github.com/robertsLando/pkg-binaries

@hipstersmoothie
Copy link
Contributor

PKG only supports lts non-odd versions of node. Contributors are currently working on 14 support which should include modules

@dement6d
Copy link

Same issue node v13.14.0

@dement6d
Copy link

Maybe this can help: https://github.com/robertsLando/pkg-binaries

There are no node 13 binaries for windows there....?

@robertsLando
Copy link
Contributor

Use an LTS version instead

@dement6d
Copy link

Use an LTS version instead

I'm unable to use an LTS version due to a package i use, iohook. I can't get it to work with any node version other than 13.14.0

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests