Open samdeane opened 3 months ago
Update: manually deleting the previous pubspec_overrides.yaml
file in the velocity_flutter
package seems to fix this problem.
The old file was using flow-stye YAML. The new file isn't:
It looks like your version accidentally ends in a dot? ^1.0.0.
, can you try removing the last dot and re-run bootstrap?
Ah - I think that must be an artefact of my copying & pasting into this bug report. I have linting on in vscode and I think I would have spotted the warning:
That said, I tried putting the extra dot back and running bootstrap, and it coped!
Update: manually deleting the previous
pubspec_overrides.yaml
file in thevelocity_flutter
package seems to fix this problem.
Very odd that it was generating that before, this can be closed now then I guess?
I think running melos clean && melos bootstrap
should also have solved it.
Is there an existing issue for this?
Version
5.3.0
Description
I have a working project containing a couple of apps, and some existing internal packages.
I've now added a native flutter plugin package to it locally.
The plugin was created by:
flutter create --org games.formation --template=plugin --platforms=android,ios,macos -a kotlin -i swift velocity_native
and is virtually unmodified from that template.Running
melos bootstrap
works fine if I don't reference the package from any other packages' pubspecs.It also works fine if I add the package as a dependency to the pubspec of one of the applications.
However, if I add it as a dependency to the pubspec of one of my other internal packages:
the following exception is thrown when running
melos bootstrap
:Steps to reproduce
I don't currently have a repro case which doesn't involve our code - which I can't share.
Expected behavior
melos should complete normally:
Screenshots
No response
Additional context and comments
No response