Open frasercl opened 3 months ago
Summary from discussion between Cameron, Dan and me:
When we make this move we also want to account for where the website logic should live. (website (aka app or standalone app), viewer-component, viewer-core)
Something like this:
packages/
viewer-core/
src/
package.json (viewer-specific dependencies)
viewer-component/
src/
package.json (component-specific dependencies)
website/ (or app or standalone-app)
src/
(webpack config)
package.json (website-specific dependencies)
package.json (shared dev dependencies)
Use Case
We've got two repos, one for the viewer implementation, one for its frontend UX. We have to publish one to NPM to get new features in the other.
Solution
Unify these projects in a single repo. They could remain separate NPM packages this way, but share build configs and dependencies.
Alternatives
They could just become the same package too?