[mabaasit]

Exports toJSString separately. Currently the default export pulls in the worker code and it breaks vscode integration. We can fix it on the vscode side using webpack, but this is cleaner.

Description

Open Questions

Checklist

• I have signed the Contributor License Agreement (https://www.mongodb.com/legal/contributor-agreement)
• New tests and/or benchmarks are included
• Documentation is changed or added

[Copilot]

🟢 Approval recommended

The additive export and bundle mappings preserve existing entry points, with no unresolved issues identified.

No open issues 🎉

What changed in this PR

Adds a dedicated stringify entry point to shell-bson-parser, allowing VS Code consumers to use toJSString without pulling in worker code.

Changes:

• Adds subpath exports and TypeScript type mappings while preserving existing root exports.
• Adds a CommonJS bundle entry for stringify.
• Adds a test asserting that the stringify module exports only toJSString.

File	Description
packages/​shell-bson-parser/​webpack.cjs.config.cjs	Builds the standalone CommonJS stringify entry.
packages/​shell-bson-parser/​src/​stringify.spec.ts	Checks the stringify module’s export surface.
packages/​shell-bson-parser/​package.json	Exposes the stringify subpath and its types.

_{Review effort: Balanced}