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

Wrap mix version task with production conditional #2405

Closed
wants to merge 1 commit into from

Conversation

knowler
Copy link
Member

@knowler knowler commented Feb 15, 2020

I had previously removed this (#2268) since from a quick glance at the actual Mix source code for the component, it seemed that this task only ran in production. I have recently discovered that without the conditional, versioning indeed does take place in development (see the mix-manifest.json).

I had previously removed this since from a quick glance at the actual
Mix source code for the component, it seemed that this task only ran in
production. I have recently discovered that without the conditional
versioning indeed does take place in development (see the
`mix-manifest.json`).
@knowler knowler requested a review from Log1x February 15, 2020 21:51
@Log1x
Copy link
Member

Log1x commented Feb 29, 2020

Yeah, I hadn't noticed this either. Perhaps we just leave it? I don't see an issue with it seeing as it's a non-issue with BrowserSync and it's only busting with a query param. Thoughts?

@knowler
Copy link
Member Author

knowler commented Feb 29, 2020

I don't see an issue with it seeing as it's a non-issue with BrowserSync and it's only busting with a query param.

Ya, it’s not a super big deal.

@knowler knowler closed this Feb 29, 2020
@knowler knowler deleted the revert-remove-mix-version-conditional branch February 29, 2020 23:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants