chore(components): update eslint & prettier setup

[aklkv]

📌 Summary

It addresses two things

• aligns to blueprint eslint/prettier
• as a result of above addon is fully ready to start writing gts files whenever team is ready. This changes are coming to app it self as part of the next LTS as well but thanks to pnpm dependency isolation seems to work great we can gradually upgrade workspaces one by one

🛠️ Detailed description

📸 Screenshots

🔗 External links

Jira ticket: HDS-XXX
Figma file: [if it applies]

---

👀 Component checklist

• Percy was checked for any visual regression
• A changelog entry was added via Changesets if needed (see templates here)

💬 Please consider using conventional comments when reviewing this PR.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
hds-showcase	✅ Ready (Inspect)	Visit Preview	Mar 18, 2025 9:35pm
hds-website	✅ Ready (Inspect)	Visit Preview	Mar 18, 2025 9:35pm

[alex-ju]

The proposed changes in terms of setup look good overall, aligning us with the ember blueprint.

The main reason I'm not in a position to approve yet, is the prettier bump – 3.5 is more opinionated on Sass to a point where a single change (the 'Break before breaking comma separated values', poorly implemented in my opinion) results in things like inline comments being misplaced, messing up the readability of the code. And it doesn't seem to provide a way to disable this rule via config.

I'm going to highlight a few such changes that I'm not fond of:

I appreciate prettier 3.5 also comes with support for TypeScript configuration file, which is great, so I see the tradeoffs we'll have to make.

I will bring this PR to engineers attention during our sync today and aim to come up with a resolution.

[alex-ju]

Tried my best to preserve those inline comments in CSS via prettier config to no avail, so I re-positioned them manually in 3bca98a in a way that hopefully makes sense to everyone. Comments are now either before the line or in line, never after the line.

In regards to the eslint errors, I disabled them in 9a824a3 and captured them in HDS-4656 to facilitate the upgrade preventing us from introducing new errors.

[didoo]

The proposed changes in terms of setup look good overall, aligning us with the ember blueprint.

The main reason I'm not in a position to approve yet, is the prettier bump – 3.5 is more opinionated on Sass to a point where a single change (the 'Break before breaking comma separated values', poorly implemented in my opinion) results in things like inline comments being misplaced, messing up the readability of the code. And it doesn't seem to provide a way to disable this rule via config.

Can we find a way (eg. open a PR/request/issue upstream) to avoid messing up with the Sass format, in particular the comments? For a CSS developer comments deliver a lot of meaning to the code (and their location too). The alternative for me is to have a different automation for Sass files that is less opinionated/restrictive/destructive.

[aklkv]

I can prettier ignore all scss files for now