-
Notifications
You must be signed in to change notification settings - Fork 81
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
webdev build
should output by default
#27
Comments
Hrm...perhaps... |
As mentioned in the recent bug filed on package:build I would be in favor of this. I do also agree that |
Ok, I'm going to add support for |
Ack
…On Tue, May 22, 2018 at 4:09 PM Andrew Lorenzen ***@***.***> wrote:
Ok, I'm going to add support for --output NONE to disable output, and
then set the defaults to NONE for serve and web:build for build.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABCikFUTXWfB8SHRdHqYOsGfdhX6I9sks5t1JqPgaJpZM4TI33e>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Discussed in an internal thread. For users of builders that are only going to source it isn't always necessary to use
--output
, but web users generally want to build a deployable directory.Question is whether we want to wait for the new build_runner and by default add
--output web:build
Should also allow
--output NONE
to get no output and not forward tobuild_runner
.The text was updated successfully, but these errors were encountered: