Closed curiosbasant closed 2 years ago
I also experienced this issue and solved it by switching node to the LTS version. Shout out to the asdf library which allows switching between different node package versions globally and by directory as easily as asdf local nodejs lts
.
I also experienced this issue and solved it by switching node to the LTS version. Shout out to the asdf library which allows switching between different node package versions globally and by directory as easily as
asdf local nodejs lts
.
Hey thanks, but I do have node v17.2.0 installed, isn't that enough?
I also experienced this issue and solved it by switching node to the LTS version. Shout out to the asdf library which allows switching between different node package versions globally and by directory as easily as
asdf local nodejs lts
.Hey thanks, but I do have node v17.2.0 installed, isn't that enough?
The LTS version stands for "long-term support". In nodejs's case this "guarantees that critical bugs will be fixed for a total of 30 months," other libraries might define it slightly differently. Right now the LTS node version is 16.13.1.
Thanks, installing lts for node, did solved the issue.
I've cloned this repo demo, and tried to run it with![image](https://user-images.githubusercontent.com/49369883/147966885-46529226-faca-4954-8a62-2306b38cd0b0.png)
yarn dev
, but it is not working and giving the following error.