-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Project status #294
Comments
@lukebatchelor any insight? |
Hey @Offirmo , @ahmedelgabri Sorry about the delay there. It's a good question for sure. There isn't anyone actively working on improving bolt day to day right now. Specific pieces are picked up as they're needed by companies who are using it essentially. There's definitely a ton of room for improvement, but at this point there's not much incentive to fix some of the glaring gaps. Definitely not to say it's abandoned, I'm still happy to watch the repo, respond to people and look at good faith PRs, it's just mostly in my own time at this point. In terms of choosing between the two, like you said, it's very easy to switch. The biggest differences are definitely bolt's strictness which is 100% non-negotiable when you get to a repo of the kind of size we're dealing with (480+ packages, I think around 1.5M loc) and then some nice tooling around upgrades, publishing and task running. Does that help at all? Happy to chat if not. |
Thanks, @lukebatchelor for the update. |
I recently completed a brief tour of Atlassian as a front-ender and their rather large frontend monorepo, which contains all the Atlaskit packages plus many more internal packages, was my first real exposure to monorepos. It’s managed by Bolt. It may not be the most popular monorepo manager at the moment, but Atlassian is heavily invested in Bolt. I recently selected Bolt to manage a new frontend monorepo at my new job. I like its simplicity and strictness. It’s early days, but so far it’s going well. |
Hey everyone 👋🏼 ,
I'm in the middle of evaluating different monorepo tools & I think
bolt
is leading the pack here for my use case. But I wonder what's the current status of the project? I can see some minor changes happening still from time to time. But there also a lot of issues & interesting ideas discussed even from 2018 with no action (for example #78), some commands are not implemented yet & the lack of documentation (bolt --help
would be useful to help with this point but it's not implemented)I know that it will be easy to switch from
bolt
toyarn
workspaces if needed because they are nearly identical. But I'm curious to know about the current state & if there are any future plans for the project.The text was updated successfully, but these errors were encountered: