7 Matching Annotations
- Mar 2024
-
yarnpkg.com yarnpkg.com
-
when projects want to keep strict boundaries within their code and avoid becoming an entangled monolith. This is for example the case for Yarn itself, or many enterprise codebases.
-
- Jul 2021
-
github.com github.com
-
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
-
medium.com medium.com
-
There’s several benefits to splitting code into multiple packages, whether it be a library, micro-services or micro-frontends.
-
-
www.chevtek.io www.chevtek.io
-
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.
Tags
- sound/reasonable/wise/defensible
- composability
- why not?
- composition
- monolithic/giant 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)
- core/guiding beliefs/values/principles/philosophy/ideology
- microlibraries
- easy to maintain
- making changes / switching/migrating gradually/incrementally/step-wise/iteratively
- small units/components/modules/libraries/packages/projects
- micropackages
Annotators
URL
-