@modular/<packages>

First, the bad news. @modular is not an available scope. So this exercise is mostly theoretical, but useful if we can figure out another scope.

(I’m also still trying to get the modular package name, but got busy actually building this thing. Will follow up again.)

Anyway…

---

I maaay be changing my mind about scoping our packages. Maybe a namespace/scope is the way to go. We can still keep the name of the binary as modular, but I don’t like the multiple syllable corner we’ve backed ourselves into by following CRA’s lead (also honestly, create-react-app isn’t that great a name. It’s very utilitarian, which is good, but isn’t meant to be an inspiration.) Here’s a proposal for cleaner package names :

@modular/create - replaces create-modular-react-app @modular/template - replaces cra-template-modular-typescript Users never see this, but still. @modular/cli - replaces modular-scripts, tho it can still be called with modular like it is now. @modular/eslint-config - replaces eslint-config-modular-app

(If we were ultra ambitious, we could also consider merging @modular/create and @modular/cli. But one thing at a time.)

Besides, I’m thinking we should lean into scopes for generated repositories as well (https://github.com/jpmorganchase/modular/issues/76) and it would be weird if we didn’t follow our own recommendation.

(On that note, wish we could use modular to manage modular. Really loving using it otherwise.)

Open to discussion, hit me with your best shot.

[sebinsua]

@modular-tools/?

[threepointone]

How about @jpmodular