question-mark
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.

Specify requirement to use Node.js version 16.x

See original GitHub issue

I tried this on Node v14 and it failed to run, erroring with

couldn't do the magic. please read the notes in README.md, restart your device and try again
TypeError [ERR_UNKNOWN_ENCODING]: Unknown encoding: base64url
    at Buffer.toString (buffer.js:803:11)
    at /Users/robin/dev/margerine/src/exploit.js:1:81335
    at new Promise (<anonymous>)
    at /Users/robin/dev/margerine/src/exploit.js:1:76415
    at async /Users/robin/dev/margerine/margerine.js:49:16
    at async wrapSentry (/Users/robin/dev/margerine/src/utils.js:134:5) {
  code: 'ERR_UNKNOWN_ENCODING'
}

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
robinduckettcommented, Mar 26, 2022

+1 for engines definition - not everyone uses nvm (although I do).

On Sat, 26 Mar 2022, 10:32 Philipp Molitor, @.***> wrote:

You could also improve at the following points:

when using NVM, add a .nvmrc file, which tells NVM which version is required https://stackoverflow.com/questions/57110542/how-to-write-a-nvmrc-file-which-automatically-change-node-version

For plain Node.js, add the engines property to the package.json: https://docs.npmjs.com/cli/v7/configuring-npm/package-json#engines

— Reply to this email directly, view it on GitHub https://github.com/fpv-wtf/margerine/issues/6#issuecomment-1079658192, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAEMJ525HIBMXM7Y2YVP6DVB3RTRANCNFSM5RL3G5PA . You are receiving this because you authored the thread.Message ID: @.***>

0reactions
PhilippMolitorcommented, Mar 26, 2022

You could also improve at the following points:

when using NVM, add a .nvmrc file, which tells NVM which version is required https://stackoverflow.com/questions/57110542/how-to-write-a-nvmrc-file-which-automatically-change-node-version

For plain Node.js, add the engines property to the package.json: https://docs.npmjs.com/cli/v7/configuring-npm/package-json#engines

Read more comments on GitHub >

github_iconTop Results From Across the Web

How can I specify the required Node.js version in package.json?
You can set the engines field in your package.json and set requirements for either node or npm versions or both: "engines" : {...
Read more >
Node.js default version is now 16.x - Heroku Dev Center
You should always specify a version of Node (as illustrated here), but if you do not, Node.js 16 will be installed for you....
Read more >
How to define the required Node.js version in package.json?
To define the required Node.js version in the package.json file we will have to go through few simple steps:.
Read more >
Download - Node.js
Latest LTS Version: 18.12.1 (includes npm 8.19.2). Download the Node.js source code or a pre-built installer for your platform, and start developing today....
Read more >
Switching between Node versions during development
We compare and contrast two popular Node version managers that can help you more easily switch between Node versions during development.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found