add currencyformatter.js@1.0.4 w/ npm auto-update

[nolsherry]

@kennynaoh, please help me review this PR, thanks!

Checklist for Pull request or lib adding request issue follows the conventions.

Note that if you are using a distribution purpose repository/package, please also provide the url and other related info like popularity of the source code repo/package.

Profile of the lib

• Git repository (required): https://github.com/osrec/currencyFormatter.js
• Official website (optional, not the repository): https://osrec.github.io/currencyFormatter.js/
• NPM package url (optional): https://www.npmjs.com/package/currencyformatter.js
• GitHub / Bitbucket popularity (required):
  • Count of stars: 289
  • Count of watchers: 13
  • Count of forks: 15
• NPM download stats (optional):
  • Downloads in the last day: 1
  • Downloads in the last week: 14
  • Downloads in the last month: 58

Essential checklist

• I'm the author of this library
  • I would like to add link to the page of this library on CDNJS on website / readme
• This lib was not found on cdnjs repo
• No already exist / duplicated issue and PR
• The lib has notable popularity
  • More than 100 [Stars / Watchers / Forks] on [GitHub / Bitbucket]
  • More than 500 downloads stats per month on npm registry
• Project has public repository on famous online hosting platform (or been hosted on npm)

Auto-update checklist

• Has valid tags for each versions (for git auto-update)
• Auto-update setup
• Auto-update target/source is valid.
• Auto-update filemap is correct.

Git commit checklist

• The first line of commit message is less then 50 chars, be clean and clear, easy to understand.
• The parent of the commit(s) in the PR is not old than 3 days.
• Pull request is sending from a non-master branch with meaningful name.
• Separate unrelated changes into different commits.
• Use rebase to squash/fixup dummy/unnecessary commits into only one commit.
• Close corresponding issue in commit message
• Mention related issue(s), people in commit message, comment.

close #9210, cc @osrec

[kennynaoh]

@nolsherry
The latest version on git repo is v1.0.4.
Please confirm with author whether he/she can published the latest version on npm.
Thanks!

[nolsherry]

@kennynaoh, OK, I will confirm with the author.

[osrec]

Latest version published to npm :)

[PeterDaveHello]

@osrec Thanks

[nolsherry]

@kennynaoh , I have updated to the latest version v1.0.4, please help me review this PR, thanks!

[kennynaoh]

@nolsherry
Please manually add old versions from git repo, because some of versions can't get from npm.
Thanks!

[nolsherry]

@kennynaoh , the author has updated all versions to npm, please try to use auto-update.js to get all repo versions from npm, thanks!

[kennynaoh]

@nolsherry
Right, there are just two versions on npmcdn.com, but there are all versions on npmjs.com.
Sorry about that.

[kennynaoh]

LGTM
ping @PeterDaveHello