You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have an impossible number of warnings thrown at build time due to dependencies out of our control. This means that it's easy to overlook our engine enforcement -- in some cases it's not even visible due to standard out windowsizes!
NPM provides a configuration to make engine enforcement more concrete with the .npmrc file
The text was updated successfully, but these errors were encountered:
Use a node version of 10 or 16. Attempt to install with npm install
Reference openmct in a another project which builds from source: viper-openmct, VISTA?
I tested this with node 16 and got this error, so looks good to me! Testathon on 02/14/2022
npm ERR! engine Not compatible with your version of node/npm: [email protected]
npm ERR! notsup Not compatible with your version of node/npm: [email protected]
npm ERR! notsup Required: {"node":">=12.20.1 <15.0.0"}```
Summary
We have an impossible number of warnings thrown at build time due to dependencies out of our control. This means that it's easy to overlook our engine enforcement -- in some cases it's not even visible due to standard out windowsizes!
NPM provides a configuration to make engine enforcement more concrete with the
.npmrc
fileThe text was updated successfully, but these errors were encountered: