Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@bc-chaz
Copy link
Contributor

@bc-chaz bc-chaz commented Aug 11, 2022

What?

Fixes an issue with Node's fs/promises module import. Essentially, this issue is corrected in Node 14+ - the fix for Node 12 is to remove /promises from the import.

NOTE: this PR also removes the initial npm build from the generate command - this was creating issues since the types were no longer there.

Tickets / Documentation

APPEX-304

Testing

verified locally by running linting

cc @bigcommerce/gta-dt

@bc-chaz bc-chaz added the wip work in progress PRs, not ready for review label Aug 11, 2022
@bc-chaz bc-chaz force-pushed the appex-301 branch 14 times, most recently from b7750b4 to 6a85020 Compare August 11, 2022 22:19
@bc-chaz bc-chaz removed the wip work in progress PRs, not ready for review label Aug 11, 2022
Copy link
Contributor

@bc-zachary bc-zachary left a comment

Choose a reason for hiding this comment

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

One clarification, but looks good otherwise! 👍

} catch (err) {
assertIsError(err);
process.stderr.write(`${sourceFile}: ${err.name}: ${err.message}\n`);
process.stderr.write(`${sourceFile}: ${err.name}: ${err.message}}\n`);
Copy link
Contributor

Choose a reason for hiding this comment

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

Not sure if intentional. Is there an omitted closing brace in err.message?

Suggested change
process.stderr.write(`${sourceFile}: ${err.name}: ${err.message}}\n`);
process.stderr.write(`${sourceFile}: ${err.name}: ${err.message}\n`);

Copy link
Contributor Author

Choose a reason for hiding this comment

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

good catch - I was mucking around with error output (trying to resolve the issue removing the auto-gen files) and left this.

strategy:
matrix:
node-version: [12.x, 14.x, 16.x, 17.x]
node-version: [12.x, 14.x, 16.x, 18.x]
Copy link
Contributor

@matthewvolk matthewvolk Aug 12, 2022

Choose a reason for hiding this comment

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

🍹 Should we keep 17.x in there? I'm also wondering if we should just get rid of 12.x since it's no longer maintained (security support ended earlier this year)

Copy link
Contributor

Choose a reason for hiding this comment

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

17.x isn't an LTS version and is no longer supported. I believe it reached end of life in May or June.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

17 is indeed no longer supported so I bumped this to 18. I definitely think we should look into dropping 12 - I'd like to capture that in a separate PR (I'm already a bit out of scope with removing the auto-generated types files)

matthewvolk
matthewvolk previously approved these changes Aug 12, 2022
Copy link
Contributor

@matthewvolk matthewvolk left a comment

Choose a reason for hiding this comment

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

LGTM 👍 Thanks for going down the rabbit hole on this one with the generated files!

Copy link
Contributor

@bc-zachary bc-zachary left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@bc-chaz bc-chaz merged commit 2073c2f into main Aug 15, 2022
@bc-chaz bc-chaz deleted the appex-301 branch August 15, 2022 23:26
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.

4 participants