fix: expand dotenv names containing null - #21898
Conversation
🦋 Changeset detectedLatest commit: e619c55 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Warning Review limit reachedNext included review available in 37 minutes. View limit detailsLimit details: You’ve used all 10 included reviews currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (4)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Dotenv expansion split expressions with a null delimiter when no operator existed, so a variable name containing lowercase
nullwas broken into unrelated fragments. Operator-free expressions now remain whole before lookup.What kind of change does this PR introduce?
fix
Did you add tests for your changes?
Yes. The real dotenv config case expands a reference to
WEBPACK_null_VALUE. The focused integration run passes 112 tests, and all lint, generated-output, type, format, spelling, changeset, diff, and final-newline checks pass.Does this PR introduce a breaking change?
No. Valid variable names now expand correctly.
If relevant, did you update the documentation?
A patch changeset documents the expansion correction. No public documentation change is required.
Use of AI
Significant AI assistance was used to audit dotenv expansion and draft the fix and regression coverage. I reviewed the final diff and verification results.