Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Monorepo?
See original GitHub issueToday the official Hyperapp ecosystem consists of four different repositories hosted in the same organization. The supporting libraries all have devDependencies and peerDependencies on particular versions of hyperapp that need to be kept up-to-date. Managing them all as a single repository would allow for refactoring/testing/releasing compatible versions of all at once. Perhaps this coordination isn’t too painful with four packages, but it’s still there.
Monorepos are already used by many successful projects like Babel, React, Angular, Ember, Meteor, Jest, and others. If we decided to move forward with this approach, there are tools to assist with managing multiple packages in a single repo such as Lerna.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Keeping the repositories separate seems fine. Especially now that the API is likely to be stable.
I vote no. Our current structure works, and I have seen a lot of orgs work like we do. Especially Vue/Webpack 🎉