Closed orschiro closed 8 years ago
Thats because the script you referenced is concatenated and minified by the grunt toolchain (sort of a make for javascript) on the developers machine - if he calls grunt. Actually, the build product (jetzt-solid.min.js) should not be checked in git. Like now, one would need to run grunt before each commit, so it is up-to-date with the sources.
Cleaner would be building on a build server (e.g. travis or cloudbees, which offer auto-hooking in github) that rebuilds after each commit and that can update the gh-pages branch (und thus https://ds300.github.io/jetzt/jetzt-solid.min.js).
@h0ru5
Interesting. Thanks. So the required source for the bookmarklet always needs to pushed to a separate gh-pages to make it working?
There is no other way around this?
the gh-pages branch is actually what is served from github.io, where the bookmarklet looks for the jetzt-solid.min.js
the essence of my post above is:
so if you refer to the solid.min.js from master (as you bdo above), you still need to "recompile" it whenever one of the source file changes
@h0ru5
Thanks, now I got it!
So this isn't an issue right?
Dear @peteruithoven,
Indeed, no longer an issue.
Thanks for closing!
~Robert
Hi there,
I modified the original bookmarklet to point to the source files in the repo in order to use the recent pull merge.
Original bookmarklet code:
I modified it to this to make sure that it fetches the latest content:
However, the behaviour of the bookmarklet is still not the same as if I clone the repo and use the extension approach instead.
Can anyone please explain to me why that is?