Skip to content

Conversation

ctcpip
Copy link
Contributor

@ctcpip ctcpip commented Aug 7, 2025

No description provided.

Copy link
Member

@wesleytodd wesleytodd left a comment

Choose a reason for hiding this comment

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

Any reason not to just call this an integration test? I understand that it is not, but it feels like adding a new stage in the workflow is a bit overkill for the need here. I agree it is a good test, but just was wondering why all the rest. Not blocking and if you feel like defending it or just not wanting to undo it I am fine either way.

@ctcpip
Copy link
Contributor Author

ctcpip commented Aug 8, 2025

what's it's called/named isn't really important, but we don't want to bundle it with integration tests because those can't run everywhere. and the reason I didn't just add it to the existing test step is because this doesn't need to run in all node versions

@wesleytodd wesleytodd merged commit 20fb486 into pkgjs:main Aug 8, 2025
7 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.

2 participants