-
Notifications
You must be signed in to change notification settings - Fork 570
Building tags not work as thought for gopherjs build
#598
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
Comments
This is likely related to #559 . GopherJS's caching is broken in several ways. A work-around is to always clear the cache when building--perhaps manually, or as part of a build process (such as a Makefile).
is what I use to accomplish this. |
@flimzy Thanks for your suggestions.
As in oskca/gopherjs-vue#6, is there a good way to switch different versions of |
gopherjs build
gopherjs build
See my comment on #468 on a potential work-around for that issue. |
#468 (comment) does not work for my situation, in my case I just want the following 2 CMDs produce different output, but in fact the output will not change:
unless you change the code in |
That sounds like the caching bug(s) are less harmless than previously thought, since it affects valid code that's compiled with different builds tags. Fixing this would be desirable. |
Also related: #620 |
I've fixed #559 just now. That may or may not be sufficient to resolve this issue too. Is it possible for you to check if this issue still occurs with latest GopherJS? |
Well, this issue still exists |
Thanks for confirming. Is it possible for you to make a more minimal (ideally, without too many outside packages) reproduce sample that demonstrates the problem? For a good example, see #559 (comment). |
This continues to bite me, despite my best efforts to work around it. Would it be reasonable to disable caching unless/until this bug can be fixed? |
I think (but haven't confirmed) that disabling caching may be a large and invasive change, which might be no less work and risk than investigating and fixing the bug in the first place. Is it possible for you to create a way to reproduce this issue @flimzy? (FWIW, I have not seen any issues with build caching.) |
In my tests, it seems build tags are ignored if the minify flag is provided. |
Uh oh!
There was an error while loading. Please reload this page.
In my VueJS binding project Vuejs, I tried
to include different version of
Vue Javascript Code
using go building tags,but the generated js code does not change with or without building tags.
I hava tow files to switch tags: inc_debug.go
and inc_minified.go
Steps to show the problem
If you swap setp 3 and step 2
the generated js code would only include the
vue-2.1.10.min.inc.js
I also tried building tags in *.inc.js, but it not work as #468
The text was updated successfully, but these errors were encountered: