-
Notifications
You must be signed in to change notification settings - Fork 9
Aduh95 #17
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
|
@aduh95 ... Just wanted to get a sense of what this PR is working towards. Want to have context for a review. This is used by workers and bun also so need to know if there are significant changes that would require attention there also |
|
The end goal would be to be able to build it as a shared lib and use it in node (in the test-shared workflow), and make node depend on this repo. The current state is that I'm able to build it as a shared lib, but static build seems broken from the looks of CI, I haven't investigated further. |
Currently the code is maintained in two different repos (nodejs/node and nodejs/ncrypto) which are slightly diverging, and do not support building as a shared lib.
The end goal would be to be able to build it as a shared lib and use it in nodejs/node (in the test-shared workflow), and make node depend on this repo (i.e. to update nodejs/node, changes would need to first land here).
FWIW I didn't intend to open this, I was planning in sending in separate PRs, but I opened it by accident so I figure I might as well keep it as draft until I get a green CI so I can start sending dedicated PRs.