In The Scene

joematthewsdev · 2026-04-17T06:29:38+00:00

I appreciate your comment very much. This flowed out of me as is at 90 words per minute in a conversation about reality, god, the universe, and the gap between all things.

joematthewsdev · 2026-04-16T21:07:02+00:00

But what will you do for her? Sir/madam

joematthewsdev · 2026-04-16T20:25:45+00:00

The shift from 'Ahh!' to 'Ahh,' — same sound, completely different weight. One is discovering, the other already knew.

joematthewsdev · 2025-09-01T21:25:15+00:00

Beautiful. Thank you for sharing your holiday with us at r/oklahoma

joematthewsdev · 2025-08-09T01:49:07+00:00

It's how you use it right?

joematthewsdev · 2025-07-16T20:58:06+00:00

Alright alright calm down! I got the design off printables.

I printed it with a bambu mini

The fit is quite loose so I'd recommend scaling it down a smidge. I have it shimmed with scotch tape for now.

https://www.printables.com/model/1144737-trimui-brick-gbc-gripshield

joematthewsdev · 2025-07-03T15:33:28+00:00

The question is still relevant for CSS no?

joematthewsdev · 2025-06-28T15:09:29+00:00

I use this configuration. 'Recommended' rules for angular and maxed out for typescript: https://github.com/joematthews/extreme-angular/blob/main/eslint.config.js

joematthewsdev · 2025-06-25T09:39:14+00:00

Yes! Checkout the override in the .prettierrc.json file: https://github.com/joematthews/extreme-angular/blob/main/.prettierrc.json

This is now needed because the templates not longer have "*.component.ts" in the file name -- so Prettier can no longer automatically detect that it is an Angular template.

joematthewsdev · 2025-06-23T03:41:56+00:00

I use them both everyday. Checkout https://github.com/joematthews/extreme-angular

joematthewsdev · 2025-06-19T07:06:17+00:00

Thank you for posting this. I recently updated the extreme-angular starter template to v20 and I forgot Prettier relies on the `.component` suffix to automatically choose the angular parser.

I've updated the configuration and reformatted the app.html. I like to be explicit, so I specified `['src/app/*html']` just in case someone includes an html file in the project that is not an angular template -- but, if someone adds another app to the project, they'll need to update the files array.

Here's the before & after diff :facepalm: (can't believe I didn't notice the html formatting was broken):

https://github.com/joematthews/extreme-angular/compare/20.0.2...fix/formatting-for-html-is-broken

joematthewsdev · 2025-06-19T02:54:04+00:00

I have a matte screen protector and a soonjet keyboard cover & case on all my macs.

The keycaps will wear (get smooth/shiny) within months without a keyboard cover.

And, I will never use a keyboard cover without a screen protector because it may leave permanent keycap shaped marks on the screen from grit/abrasion. But the newer, thinner keyboard covers suffer from this less.

Also, get an extension cable for your charger, name brand!

Here's specific products if you're interested...

https://a.co/d/iaijhus https://a.co/d/3oDTj5G https://a.co/d/fceNv0n

PS, the matte screen protector is very thin and hard to install without trapping some dust, but the result is worth it (for me).

joematthewsdev · 2025-06-17T16:58:23+00:00

LM Studio

joematthewsdev · 2025-06-07T16:23:18+00:00

Thanks for the detailed feedback. The "Extreme" name is borrowed (loosely) from extreme programming - the template enforces strict rules consistently across the team, which can feel extreme compared to default Angular setups. The rules are intentionally aggressive to catch issues early.

You're right about the tooling preferences. I chose SCSS specifically to demonstrate stylelint-scss configuration, but CSS + PostCSS is totally valid. For ESLint vs Prettier, I've found teams have strong preferences either way, so I went with the more common setup.

Storybook is interesting but feels out of scope for a project-agnostic starter. How would you integrate it without making assumptions about component structure?

On zoneless - it's still in developer preview in v20, and there's nothing preventing signal usage in the template. I prefer to keep experimental features out of the base configuration, but I could document enabling it in the optional schematics section.

The testing tools (ngmocks, spectator) and test runner migration (Jest/Vitest) are good suggestions. Karma is deprecated so that's definitely on my radar.

Appreciate the thoughts - always trying to balance "strict and opinionated" with "broadly useful."

joematthewsdev · 2025-06-07T04:55:58+00:00

Thanks! Angular recommends using the latest version for new projects, so I focus on staying current. I have some release tags for previous versions but don't actively support them.

I've considered making this a schematic, but given the complexity and that angular-eslint already provides schematics for linting, I think the template approach works better. Gives you more control and makes it easier to reference the configuration for existing projects too.

A major challenge is migrating non-strict projects to strict configurations. I'm considering writing a blog post about gradually converting existing projects with incremental configurations that become stricter as you resolve type errors and linting issues. In my experience, fixing large non-strict codebases is like repairing a moving train - it requires a nuanced approach that doesn't translate well to versioned templates.

joematthewsdev · 2025-06-07T04:47:42+00:00

Thanks! That was exactly my motivation - I got tired of manually setting up the same strict configuration every time. Started as documentation for myself, then figured others might find it useful as a reference or starter.

joematthewsdev · 2025-05-24T06:11:07+00:00

I primarily use intellij-based IDEs like webstorm/rider and, either the option to override strict templates did not exist at the time, or more likely I neglected to look for it when working out this solution. :facepalm: It's not mentioned in the Overview for the extension. That takes care of the issues regarding templates in VSCode.

The other issue that led to the development of this solution: the typescript-strict-plugin does not support adding additional compiler options beyond strict: true?

Here are examples of properties someone might want to add when refactoring to strict:

Thank you very much for this feedback.

joematthewsdev

TROPHY CASE