Albin PK
Albin PK
The generated Dart code is not null-safe, making it unusable in modern projects
I've made a Mason brick to bootstrap a Melos project structure with poly-repo support, maybe useful while the `melos init` command is in progress. https://brickhub.dev/bricks/melos
> @albinpk ah now I get the comment, you meant as a work-around until `melos init` is out? That's a good idea. :) Yes, exactly; it's a workaround until `melos...
Ya, that makes sense about the dependencies. Thanks for the clarification!
This would be a great feature for those using Melos in non-monorepo setups. I shared a related use case in [this comment](https://github.com/invertase/melos/issues/773#issuecomment-2476475135) where I use Melos primarily for versioning and...
@spydon Thanks for the clarification! Like you mentioned, if we add Melos as a `dev_dependency` in the main project itself, it may lead to version conflicts between Melos’s dependencies and...
@spydon thanks, we can isolate Melos to a `.melos` directory, so the `dev_dependencies: melos` isn’t needed in the main project for both non-monorepo and pub-workspace environments. In both cases, we...
@spydon I think this wouldn’t require any structural change from how pub workspaces are set up. What I meant was only moving the Melos local dependency into a `.melos` directory....
Got it, thanks for the clarification!