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

[FR]: Update mime package to 2.x.x and higher #579

Closed
2 tasks done
Foxpace opened this issue Oct 1, 2024 · 0 comments · Fixed by #580
Closed
2 tasks done

[FR]: Update mime package to 2.x.x and higher #579

Foxpace opened this issue Oct 1, 2024 · 0 comments · Fixed by #580
Labels
enhancement New feature or request
Milestone

Comments

@Foxpace
Copy link

Foxpace commented Oct 1, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Describe the problem

When the project uses mime package with version 2.x.x the following error is raised:

Because no versions of flutter_gen_runner match >5.7.0 <6.0.0 and flutter_gen_runner 5.7.0 depends on flutter_gen_core 5.7.0, flutter_gen_runner ^5.7.0 requires flutter_gen_core 5.7.0.
And because flutter_gen_core 5.7.0 depends on mime ^1.0.0, flutter_gen_runner ^5.7.0 requires mime ^1.0.0.
So, because example_app depends on both mime ^2.0.0 and flutter_gen_runner ^5.7.0, version solving failed.

It will block the future updates of build_runner: ^2.4.13 and higher.

Describe the solution

The pubspec.yaml should contain 2.x.x version of mime and higher incorporating the breaking changes of the package.

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@Foxpace Foxpace added the enhancement New feature or request label Oct 1, 2024
AlexV525 added a commit that referenced this issue Oct 1, 2024
## What does this change?

Fixes #579 🎯

Also update ignored files for better development experiences.

## Type of change

- [x] New feature (non-breaking change which adds functionality)
@AlexV525 AlexV525 added this to the 5.8.0 milestone Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants