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 should specify the minimum required Node.js version, by setting engines in the package.json file to the semantic versioning specification range that is compatible with calling-extensions-sdk without requiring --openssl-legacy-provider support.
Additionally, we should remove and gitignore existing .node-version files from the packages. While it is helpful in a local development setup, .node-version has yet to be adopted by nvm, and can potentially create noise for users who only require a minimum compatible version.
We should specify the minimum required Node.js version, by setting
engines
in the package.json file to the semantic versioning specification range that is compatible with calling-extensions-sdk without requiring--openssl-legacy-provider
support.Additionally, we should remove and gitignore existing
.node-version
files from the packages. While it is helpful in a local development setup,.node-version
has yet to be adopted bynvm
, and can potentially create noise for users who only require a minimum compatible version.Related to discussion in #98 (comment)
The text was updated successfully, but these errors were encountered: