-
-
Notifications
You must be signed in to change notification settings - Fork 293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release often #76
Comments
I've been using this lib for a json list of emojis, but it'd be good if it was always up to date with latest Unicode releases. I've been researching the Unicode public data, so I might be able to help out with this. I'm guessing by streamline the process, you mean actually build a process to keep this package up to date so that we can get new Unicode emojis imported automatically. I'll see if I can rewrite |
Ah sorry, I meant that I should cut a release and publish them on NPM more often. The last release was in January. :/
I don't think this library should be up to date with the latest Unicode releases as the emojis won't be supported by operating systems til a much later date. 🤔 |
@muan I'd be happy to help maintain this repo. Here's an article I wrote on automated publishing to npm: zeke.sikelianos.com/npm-and-github-automation-with-heroku/ -- that approach might be overkill for |
@muan i am pretty sure https://github.com/semantic-release/semantic-release can help u. The setup can be a little bit tricky, but I am willing to help if needed :) |
@muan I got a build process ready, it also includes translation support. It is written yet in ES5, makes it low on dependencies but the code is pretty much bloated. Should I push the PR like this or upgrade to ES6+Babel before I do it? Personally I would love to use modern JS, I am just not sure if this exceeds the scope of this project. Opinions? |
I need to streamline this process. Probably need to do some research into how other people do this.
UPDATE Process currently:
simplemap.json
and commit if neededbower.json
andpackage.json
git tag
git push --tags
npm publish
I wish these steps can be reduced to a button as we merge in tiny updates like keyword additions. 😂
The text was updated successfully, but these errors were encountered: