https://github.com/james2doyle/project-splitting
Experiments and proof-of-concepts for how to share code across projects locally
https://github.com/james2doyle/project-splitting
Last synced: 5 months ago
JSON representation
Experiments and proof-of-concepts for how to share code across projects locally
- Host: GitHub
- URL: https://github.com/james2doyle/project-splitting
- Owner: james2doyle
- Created: 2019-09-01T05:05:33.000Z (almost 7 years ago)
- Default Branch: master
- Last Pushed: 2023-03-01T20:33:10.000Z (over 3 years ago)
- Last Synced: 2025-02-24T20:00:04.509Z (over 1 year ago)
- Language: Vue
- Size: 4.62 MB
- Stars: 1
- Watchers: 3
- Forks: 0
- Open Issues: 39
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Project splitting
> Experiments and proof-of-concepts for how to share code across projects locally.
Mostly thinking about themes for sites or sharing functions. The goal is not to leverage local NPM modules and instead try to load shared code locally via folders and paths. Thankfully, webpack is pretty good at this so most of these solutions are mostly about how to configure webpack.
Options:
## Folder Based
#### Benefits:
- very clear borders
- independent dependencies, commands/scripts, tests, configs, etc.
- framework agnostic
- different versions of deps. is possible
#### Issues
- no shared dependencies
- no shared commands for building
- keeping project configs in sync can be tough (n + 1)
## ENV Based
#### Benefits:
- transparent borders
- same commands with different names (one command for all builds)
- shared dependencies, commands/scripts, tests, configs, etc.
#### Issues
- framework lock-in (because of shared deps.)
- every dependency is shared even if it isnt used in all projects
- different versions of deps. is not possible