6 Matching Annotations
- Jul 2021
Auto-Detect & install BigCommerce's stencil-cli Auto-Detect & install Meteor Auto-Detect & install Shopify's themekit
Simpler option: https://github.com/apollographql/apollo-server/blob/main/.envrc
- Mar 2021
There’s several benefits to splitting code into multiple packages, whether it be a library, micro-services or micro-frontends.
But I believe the core philosophy of tiny modules is actually sound and easier to maintain than giant frameworks.
"Functions Are Not Packages" - Well why not?
Small modules are extremely versatile and easy to compose together in an app with any number of other modules that suit your needs.
Write modules that are small. Iterate quickly.
- small units/components/modules/libraries/packages/projects
- allowing developer/user to pick and choose which pieces to use (allowing use with competing libraries; not being too opinionated; not forcing recommended way on you)
- easy to maintain
- core/guiding beliefs/values/principles/philosophy/ideology
- why not?
- monolithic/giant modules/libraries/packages/projects
- making changes / switching/migrating gradually/incrementally/step-wise/iteratively