Closed silverwind closed 8 years ago
Go for it...
The only build I use now is grunt user
as it creates the version I copy and paste into userstyles.org.
Yeah, I think we can drop the custom build as well since we have the userscript up and running.
I'll make sure to also include a version bumping mechanism that generates the changelog from recent commits. Are you fine with using a CHANGELOG.md
for that purpose?
Sure, it'll save me some work :grin:
Or, we could just drop the change log?
So, you never used usermin
? Maybe we shall I drop minification completely, until size is a concern again?
Yeah, I don't minify at all since we got a little more breathing room on userstyles.
Hmm yeah, let's drop the changelog. The commit history ought to be good enough :)
Might be a good opportunity to use shelljs.
Having used gulp
recently on one of my projects, I think it'd be a great replacement for grunt
. The nice thing about it is that you can use custom code sections everywhere in the pipeline, and the plugin ecosystem is vast, too.
If you want to work on it, I don't mind. I haven't used gulp that much but I'm sure I can figure it out.
Will follow up with something for https://github.com/StylishThemes/New-GitHub-Dark.
So,
grunt
is going a bit out of fashion and it's getting hard to find plugins. There'sgulp
but I'm not really sure I want to tie us into another ecosystem which may or may not survive in the long-term.All our tools expose a Node.js API, so I think a
build.js
script might be in order. It definitely is much more flexible thangrunt
,gulp
or evenmake
could ever be.@Mottie I'll get started on it once we know which of the current Grunt tasks we need to replicate. Do we really need the custom style generation with
build.json
? I'm not sure anyone's really using it. Also, what aboutuser
andusermin
? I think we can dropuser
? Oh, and are you usingdev
?