Unexpected token . about backport HOT 5 OPEN

@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);
}

from backport.

Hey!

It could be related to you running with sudo. I'll try to see if I can reproduce.

from backport.

I just had the same problem. It was caused by accidentally using an old node version (12). Using node 16 fixed the problem.

from backport.

Ahh, interesting. Thanks for chiming in @gigerdo .
@ct2034 Is that perhaps the same problem you are running into?

from backport.

I was using node 8 and saw the same problem. Using node 16 fixed the problem.

from backport.