-
Notifications
You must be signed in to change notification settings - Fork 1
Add N-API subproject to run node-semver test eventually #13
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amazing work! Can you add a github workflow and actually have it run on the CI?
@@ -0,0 +1,15 @@ | |||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add package-lock and use npm? Yarn might be hard to maintain in the long term.
Can you also run the shell script in tools folder to format the code using clang-format-17 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't object to have this repository added.
I'm not sure why I can't seem to make it work on Linux CI, but at least it should tell us if a node-semver test starts failing/passing |
hey @aduh95, any plans to continue working on version_weaver? |
I mean, the project still sounds interesting, but it's just hard to find time for it now that I have a job |
The idea is that we could eventually run the node-semver test suite.
Use the following commands to build: