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

chore: add support for node v18 #1173

Merged
merged 8 commits into from
Sep 27, 2023

Conversation

OjusWiZard
Copy link
Contributor

@OjusWiZard OjusWiZard commented Sep 21, 2023

Description of the changes

Fixes #1009

To add support for node v18:

  • Updated webpack to latest v5 in epk-decryption, epk-signature, request-client.js, and web3-signature packages
  • Installed crypto-browserify and stream-browserify to handle the breaking changes in webpack

There are some warnings introduced now.
Tested using node v18.17.1 and v18.18.0

@OjusWiZard OjusWiZard changed the title chore: add support for node v18 (#1171) chore: add support for node v18 and v20 Sep 21, 2023
Signed-off-by: OjusWiZard <ojuswimail@gmail.com>
@OjusWiZard OjusWiZard changed the title chore: add support for node v18 and v20 chore: add support for node v18 Sep 23, 2023
@MantisClone MantisClone enabled auto-merge (squash) September 27, 2023 02:32
Copy link
Member

@MantisClone MantisClone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for contributing! I tested the yarn run build with Node 16.18.1 and Node 18.12.1 and it worked in both cases.

I created #1178 as a follow-up to make sure that both node v16 and v18 are included in our CircleCI tests.

@MantisClone
Copy link
Member

I don't understand why the CircleCI checks aren't starting. @benjlevesque Any idea why this is happening?

@OjusWiZard
Copy link
Contributor Author

Not sure about the root cause, but the circleci dashboard shows this.
image

@benjlevesque
Copy link
Contributor

@MantisClone @OjusWiZard I don't see the error in the CircleCI dashboard, and we got a successful build a few hours ago, maybe a temporary issue on CircleCI? Can you retry?

@MantisClone
Copy link
Member

I logged into CircleCI and was able to trigger the CI by clicking "Trigger Pipeline"
image

Copy link
Contributor

@benjlevesque benjlevesque left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks!

@MantisClone MantisClone merged commit 446ca66 into RequestNetwork:master Sep 27, 2023
26 of 27 checks passed
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.

Fix build to support Node 18 without losing support for Node 16
3 participants