Skip to content

Conversation

@aduh95
Copy link

@aduh95 aduh95 commented Jan 11, 2026

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.

@aduh95 aduh95 closed this Jan 11, 2026
@aduh95 aduh95 reopened this Jan 11, 2026
@aduh95 aduh95 marked this pull request as draft January 11, 2026 18:10
@jasnell
Copy link
Member

jasnell commented Jan 15, 2026

@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

@aduh95
Copy link
Author

aduh95 commented Jan 15, 2026

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.
I've updated the OP with my plan

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.

3 participants