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

Suggest use as a dev_dependency instead of global install #2497

Open
sigurdm opened this issue Sep 25, 2024 · 2 comments
Open

Suggest use as a dev_dependency instead of global install #2497

sigurdm opened this issue Sep 25, 2024 · 2 comments
Labels
P3 A lower priority bug or feature request package:webdev triaged type-enhancement A request for a change that isn't a bug

Comments

@sigurdm
Copy link

sigurdm commented Sep 25, 2024

Why don't we recommend installing webdev as a dev_dependency? (here).

Then we could add the constraints

dependencies:
  build_runner: ^2.4.0
  build_web_compilers: ^4.0.4

And we would not have to manually validate constraints of the current apps pubspec.lock, but rely on the pub solver to do it..

Maybe I'm missing something obvious. But it seemed to work when I tried.

@bkonyi
Copy link
Collaborator

bkonyi commented Sep 25, 2024

How would users run webdev as a dev dependency (I know it's possible, I just don't remember the CLI syntax)? We could definitely recommend this approach, but we won't be able to remove support for the current workflow given most users will be activating webdev as a global package.

On a side note, I'd like to move this repository into the SDK and expose webdev through the CLI, which will remove the need for depending on webdev via pub at all.

@bkonyi bkonyi added type-enhancement A request for a change that isn't a bug P3 A lower priority bug or feature request triaged labels Sep 25, 2024
@parlough
Copy link
Member

parlough commented Sep 25, 2024

How would users run webdev as a dev dependency?

Just dart run webdev build. It's always been my preferred way of using webdev in projects, but I always assumed I was missing context on why it was suggested to install it globally.

On a side note, I'd like to move this repository into the SDK and expose webdev through the CLI, which will remove the need for depending on webdev via pub at all.

+1 This would make our web development docs/story much more straightforward and consistent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 A lower priority bug or feature request package:webdev triaged type-enhancement A request for a change that isn't a bug
Projects
None yet
Development

No branches or pull requests

3 participants