fix(repo): cleanup package-lock.json and bun.lock #1799
Merged
Conversation
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
mandarini
changed the title
mandarini
force-pushed
the
chore/cleanup-lock
branch
from
dfe5efe to
8af2ef2
Compare
grdsdev
previously approved these changes
Oct 23, 2025
mandarini
changed the title
mandarini
force-pushed
the
chore/cleanup-lock
branch
from
4c47442 to
ab73045
Compare
mandarini
force-pushed
the
chore/cleanup-lock
branch
from
ab73045 to
863ab13
Compare
mandarini
changed the title
grdsdev
approved these changes
Oct 23, 2025
mandarini
added a commit
that referenced
this pull request
Oct 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Improve integration testing.
Cleanup
package-lock.jsonfile from old dependencies, and fix issues that were ignored due to old lock file.Added
--unstable-detect-cjsflag to the Deno test scripts to handle module format compatibility issues with our locally published packages. Our packages provide both CommonJS and ESM builds, and when Deno imports fromnpm(including our local registry), it sometimes picks the CommonJS version instead of ESM. This flag enables Deno to automatically detect and properly handle CommonJS modules, allowing our integration tests to run successfully. While marked as "unstable," this flag is safe for our testing purposes - it only affects how Deno interprets module formats during import resolution, not the actual test execution or coverage. The tests pass and validate the same functionality with or without it; the flag just ensures Deno can properly load our dual-format packages.