add function to set default certificate subject for ESM compatibility#1519
Open
PriyankuBiswas-EH wants to merge 4 commits into
Open
add function to set default certificate subject for ESM compatibility#1519PriyankuBiswas-EH wants to merge 4 commits into
PriyankuBiswas-EH wants to merge 4 commits into
Conversation
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Adds a supported way to mutate the module-level defaultCertificateSubject for ESM consumers by introducing a setter function.
Changes:
- Introduced
setDefaultCertificateSubject(value)to updatedefaultCertificateSubjectfrom within the module - Documented why direct assignment to an exported
letdoesn’t work for ESM namespace imports and provided an example
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…idation and error handling
erossignon
reviewed
Jun 3, 2026
| // 3. Validate the overall shape: one or more /KEY=VALUE segments. | ||
| // Keys are one or more word characters; values may be anything except a raw slash | ||
| // (nested values would need quoting, which is out of scope here). | ||
| const subjectPattern = /^(?:\/[A-Za-z][A-Za-z0-9]*=[^/]+)+$/; |
Member
There was a problem hiding this comment.
We have a utility to parse a CN string and verify it in node-opcua-pki or node-opcua-crupt. I'd suggest reusing existing material rather than maintaining a hard-to-validate REGEXP.
We need a single source of truth.
Author
There was a problem hiding this comment.
Hi @erossignon , I updated the code as per your comment, reusing the existing function.
…prove error handling
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The "export let" in "node-opcua-common/make_subject.ts" is technically mutable from within the module, but ESM module namespace objects are frozen from the outside. The cleanest short-term fix is using require() in a CJS context. The real fix needs to come from the library itself by exposing a setter function.
The library should expose a setter function like "setDefaultCertificateSubject(value: string)" that mutates the internal variable from within the module (which is always allowed). This is the proper fix. The current design is broken for ESM consumers.