Skip to content
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

fix compatibility with node v22 #493

Merged
merged 3 commits into from
May 28, 2024
Merged

fix compatibility with node v22 #493

merged 3 commits into from
May 28, 2024

Conversation

royra
Copy link
Collaborator

@royra royra commented May 18, 2024

fixes #492

@royra royra requested a review from Yshayy May 18, 2024 16:39
@Yshayy
Copy link
Contributor

Yshayy commented May 28, 2024

Is that both backward and future compatible?

Roy Razon added 2 commits May 28, 2024 17:51
- replace import `assert` keyword with `with`, see #492
- upgrade azure package to support node v22

fixes #492
- bump packaged oclif node version to latest LTS (20.13.1)
- bump node version for CI workflows to 20.x
- keep supported version in package.json to >=18.0.0
@royra
Copy link
Collaborator Author

royra commented May 28, 2024

Is that both backward and future compatible?

checked with v18, v20 (latest LTS) and v22

- remove single usage of import assertion (import ... with/assert) which was breaking compat with older node 18 versions (see https://github.com/nodejs/node/pull/52104\#issuecomment-2000337367)
@royra
Copy link
Collaborator Author

royra commented May 28, 2024

Is that both backward and future compatible?

checked with v18, v20 (latest LTS) and v22

actually with older v18 it doesn't work.

since it's just a single place which uses the import ... with/assert syntax, rewriting to remove it.

@royra royra merged commit 316f7ef into main May 28, 2024
8 checks passed
@royra royra deleted the fix-node22-compat branch May 28, 2024 15:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: SyntaxError: Unexpected identifier 'assert'
2 participants