fix: package.json pretty print Closes #4643

[rkristelijn]

• I've read and followed the contributing guide on how to create great pull requests.
• I've updated the relevant documentation for any new or updated feature.
• I've linked relevant GitHub issue with "Closes #".
• I've added a visual demonstration in the form of a screenshot or video.

Closes #4643

[bharatkashyap]

Thanks @rkristelijn! Would a tab character be more close to pretty printing than 2 spaces? Going by https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify#using_the_space_parameter

[rkristelijn]

There is no Prettier config in the project. I’d recommend adding one using npx create-prettierrc, which defaults to 2 spaces per Prettier docs. If you prefer tabs, you can configure it there, and Prettier will ensure consistency. Do you want me to add it? I’d prefer the standard Prettier settings, but my goal was just to format package.json, so I’ll follow whatever direction you prefer.

Why 2 spaces instead of 1 tab?
• Consistency across editors – tabs can render differently depending on settings.
• Precise alignment – especially useful in nested structures.
• Industry standard – used in Next.js, MUI, Google Style Guide, and Prettier defaults.
• Prevents mixed indentation – avoiding unnecessary formatting issues.
• Aligns with JSON.stringify defaults – as mentioned in this MDN reference, 2 spaces is the convention when formatting JSON output.

Let me know what works best!

[mui-bot]

Netlify deploy preview

https://deploy-preview-4644--mui-toolpad-docs.netlify.app/

Generated by 🚫 dangerJS against 9d0d2e3