Skip to content
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

[v7.0.0-dev.2] request: update melos analyze behaviour #827

Open
1 task done
ricardodalarme opened this issue Jan 8, 2025 · 1 comment · May be fixed by #829
Open
1 task done

[v7.0.0-dev.2] request: update melos analyze behaviour #827

ricardodalarme opened this issue Jan 8, 2025 · 1 comment · May be fixed by #829

Comments

@ricardodalarme
Copy link

ricardodalarme commented Jan 8, 2025

Is there an existing feature request for this?

  • I have searched the existing issues.

Command

melos analyze

Description

Now with Pub Workspaces, commands like flutter pub get and flutter analyze can run across the entire workspace at once. This is significantly faster than the previous approach, where tools had to be run separately for each package. As a result, the current behavior of melos analyze, which runs dart analyze or flutter analyze individually for each package, feels outdated and unnecessary.

Reasoning

  • Performance Improvement: Running analysis once for the entire workspace is much faster than running it package by package.
  • Redundant Command: melos analyze no longer provides any significant benefit over Dart’s built-in commands, making it potentially unnecessary.

Additional context and comments

No response

@ricardodalarme ricardodalarme changed the title [v7.0.0-dev.2] request: [v7.0.0-dev.2] request: update melos analyze behaviour Jan 8, 2025
@spydon
Copy link
Collaborator

spydon commented Jan 8, 2025

True, I think it's time we just removed melos analyze.

@spydon spydon linked a pull request Jan 8, 2025 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants