-
Notifications
You must be signed in to change notification settings - Fork 206
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
request: Add init
command to bootstrap a melos project
#773
Comments
Should I assign you to it @exaby73? :) |
I got it :) I'll cook up something soon thank you |
I've made a Mason brick to bootstrap a Melos project structure with poly-repo support, maybe useful while the |
There is also this brick: https://github.com/ubuntu/flutter_project_template But we don't want to depend on mason for the init command. |
@albinpk ah now I get the comment, you meant as a work-around until |
Yes, exactly; it's a workaround until @spydon I’m actually using Melos in my smaller projects without a monorepo structure as well, since Melos is really useful for versioning, tagging, and changelog generation. I set it up with a simple name: <name>
packages:
- ./
command:
version:
workspaceChangelog: false Is there another recommended way to set up Melos for projects that aren’t monorepos, or could we add an option for this setup in the |
It isn't recommended to have a project directly in the root, because the dependencies of the project (and vice versa) then need to conform to the Melos version and its dependency constraints. It would be good if this could be done in a better manner, but not sure how that would be possible (and that would be related to another issue and not this one). |
Ya, that makes sense about the dependencies. Thanks for the clarification! |
Is there an existing feature request for this?
Command
melos init
Description
Running
melos init
should in theory automate the steps defined in Getting StartedReasoning
Currently setting up a melos project is very manual having to create your
pubspec.yaml
andmelos.yaml
. This newinit
command would solve thatAdditional context and comments
No response
The text was updated successfully, but these errors were encountered: