Use travis CI to publish to npm

[hirako2000]

Cumbersome to publish from local machines.
Travis should publish to npm new versions of whs.

See how: https://docs.travis-ci.com/user/deployment/npm/

Version:

• v2.x.x
• v1.x.x

Issue type:

• Bug
• Proposal/Enhancement
• Question
• Discussion

---

Tested on:

Desktop

• Chrome
• Chrome Canary
• Chrome dev-channel
• Firefox
• Opera
• Microsoft IE
• Microsoft Edge

Android

• Chrome
• Firefox
• Opera

IOS

• Chrome
• Firefox
• Opera

[hirako2000]

added the config, but my encrypted API token doesn't seem found. strange doc from Travis.
Maybe using a config variable would be easier, they say to put it in the travis file and simply encrypt it. but I see you do it differently for snyk and surge @sasha240100 .
See if you can use your own api key and get it to work.
Right now it tries to build and publish but fails with the token.

Travis will only try to deploy/publish to npmjs if it sees a tag pushed.

[hirako2000]

Deploy works, Travis will publish to npmjs on new tags applied to the dev branch.
Travis currently won't commit/push the built files.

Not currently on any branch.
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)
	modified:   build/whs.js
	modified:   build/whs.js.map
	modified:   build/whs.min.js
	modified:   build/whs.module.js
	modified:   build/whs.module.js.map
no changes added to commit (use "git add" and/or "git commit -a")

this step remains having to be done manually, also release notes needs added manually.

Closing this now. Next step would be to cover those two tasks:

• Push built files
• Automatically generate release notes from closed issues and PRs.

As part of different issues.

[sasha240100]

@hirako2000 Maybe better to make the same only for master branch? I always merge dev to it after each release

[hirako2000]

Yes that would make sense, I didn't know you released from master. that's the correct thing to do ;)