-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected token . #450
Comments
Hey! It could be related to you running with |
I just had the same problem. It was caused by accidentally using an old node version (12). Using node 16 fixed the problem. |
I was using node 8 and saw the same problem. Using node 16 fixed the problem. |
@li-boxuan Thanks for chiming in. I might be able to catch this and warn the user with something like: import semver from 'semver';
import { engines } from './package';
const version = engines.node;
if (!semver.satisfies(process.version, version)) {
console.log(`Required node version ${version} not satisfied with current version ${process.version}.`);
process.exit(1);
} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I installed the tool with
sudo npm install -g --unsafe-perm backport
.When I run
backport
, nothing happens.When I run
npx backport
i get:I created both config files according to https://github.com/sqren/backport/blob/main/docs/config-file-options.md
The text was updated successfully, but these errors were encountered: