Fix create-package to handle JSONC files

[mcmire]

Explanation

Since comments were added to tsconfig.json and tsconfig.build.json files, the create-package tool no longer works.

This commit fixes the tool by using the comment-json package to parse JSONC files while retaining comments. Note that I needed to reformat tsconfig.json and tsconfig.build.json in this PR due to the way that I need to use comment-json. If we don't do this, then the next time someone runs create-package then the diffs for these files will be large.

Manual testing steps

Run yarn create-package --name foo-controller --description "This is the FooController". It should work.

References

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Note

Fix create-package to support JSONC

• Use comment-json in scripts/create-package/utils.ts to parse and stringify tsconfig.json and tsconfig.build.json while preserving comments
• Update finalizeAndWriteData to write JSON with consistent indentation; adjust tests in utils.test.ts to expect pretty-printed output
• Reformat root tsconfig.json and tsconfig.build.json to expanded, consistently formatted references
• Add comment-json to devDependencies and update yarn.lock

^{Written by Cursor Bugbot for commit 6296348. This will update automatically on new commits. Configure here.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	comment-json@​4.5.1

View full report

[cursor]

Prettier JSON parser incompatible with JSONC comments

Medium Severity

The writeJsonFile function uses parser: 'json' with prettier, but commentJson.stringify outputs JSONC content with comments when the input object has comment symbols (parsed from real tsconfig files). Prettier's json parser doesn't support comments and would throw a parse error. The test doesn't catch this because mock data lacks comment symbols. Using parser: 'json5' instead would handle comments correctly.

 

[mcmire]

Hmm I didn't know about this. Well, if this is a problem we can try this out.