new and simpler build workflow

[stoeffel]

This removes gulp completely. I will do the same for the gh-pages branch if you like.
As you can see to release we just need to update the changelog and the version in the package.json and then run npm run release.
This will allow use to have a much shorter release cycle (it's a pain atm to publish a new version).

It also removes the build artefacts from the repo and links to npmcdn.
The built artefacts are directly in the root of the module (after publishing).
And it removes some eslint issues 😸
closes #478

I will have to check this again tomorrow, have to sleep first.
@epeli would be cool if you could review this.

[stoeffel]

wow you are fast 😄

[esamattis]

Just realized: Do we break Bower if we remove dist?

[stoeffel]

Just realized: Do we break Bower if we remove dist?

could be. It's a long time since I last used bower 😆

[esamattis]

Yeah. I haven't ever used it or personally know anybody using it.

[stoeffel]

I guess we need to add it to support bower.

[esamattis]

Meteor might require it too. Component seems to be dead https://github.com/componentjs/component#this-project-is-deprecated

[stoeffel]

I added dist again
and a new task build:clean

[stoeffel]

Sorry. Will have to sleep now.
Feel free to commit and change every thing.

[stoeffel]

@splendido do you know if meteor needs the build artefacts in the repo?

[stoeffel]

@epeli any input on this and #482. I think we have to keep dist in the repo for now.

[splendido]

@stoeffel what do you mean with 'build artefacts'?
...any file created by 'meteor publish' can be safely removed

[stoeffel]

@splendido by build-artefacts I mean every thing in the dist folder.

[splendido]

I see.
Well, if you like to continue with autopublish the answer is yes: at the time of running meteor publish the file dist/underscore.string.js must be there (see this line).

But if you could publish by hands you'd only need that file when running meteor publish which means you could build the project, publish it for Meteor and then clean up everything.

[stoeffel]

Okay. Thanks for your help. I think we should just keep the dist in the repo. Makes it easier to support meteor and bower needs it anyway.

[stoeffel]

@epeli. I think this and #482 is good to go. Do you have some time this week or next to review. I think this will speed up our release cycle. Currently it's a bit of a pain.

[stoeffel]

I will merge on Monday and will release a new version (and include some bug fix PRs.)

[stoeffel]

rebased and squashed

Will do a last review this afternoon or tomorrow and then merge and publish a patch release.

// cc @epeli any objections?

[cahrens]

@stoeffel Are you still planning to publish a patch release soon?

[stoeffel]

@stoeffel Are you still planning to publish a patch release soon?

Totally, sorry for the delay. I had to take care of my baby daughter today. I will definitely work on it tomorrow.
The new build chain should allow us to publish faster.

[cahrens]

No problem-- just curious about the timeframe. Thanks for the information!