Moves typebetter.js to a dist folder and updates the example accordingly. I figure we may as well do this now as odds are we'll want to provide a src/typebetter.js in the future and built (minified, etc.) files in dist. So this is more future planning than anything.
Adds bower.json and package.json files for (eventual) publication to the Bower and npm registries.
TypeBetter isn't yet published to either registry. @yurivictor, there are a couple steps you'll need to take in order to make that happen.
When you're comfortable tagging a release (0.0.1 being the first we're working toward), you'll want to commit and push all changes to master and do a git tag v0.0.1 and git push --tags.
Prerequisites
Install Node and npm (recommend using Homebrew for this): brew install node.
Install Bower: npm install -g bower.
Initial publication to Bower
Push everything to master, tag the release with git tag v0.0.1 && git push --tags.
That should publish to npm and you should see the package listed on your npmjs.com profile page.
You can test that this worked by running bower install typebetter and npm install typebetter in a test folder somewhere on your computer.
Publishing subsequent releases
Update bower.jsonand package.json with the new version number (e.g. 0.0.2).
Commit and push all changes to master.
git tag v0.0.2 && git push --tags
Run npm publish from the root of the project. (Bower automatically picks up new releases based on git's tags.)
:beers:
Apologies if any of the above is repetitive, obvious, or otherwise unnecessary. I wanted to be overly thorough just in case. Happy to answer any questions or help out with any problems if they arise.
This PR does a couple things:
typebetter.js
to adist
folder and updates the example accordingly. I figure we may as well do this now as odds are we'll want to provide asrc/typebetter.js
in the future and built (minified, etc.) files indist
. So this is more future planning than anything.bower.json
andpackage.json
files for (eventual) publication to the Bower and npm registries.TypeBetter isn't yet published to either registry. @yurivictor, there are a couple steps you'll need to take in order to make that happen.
When you're comfortable tagging a release (0.0.1 being the first we're working toward), you'll want to commit and push all changes to master and do a
git tag v0.0.1
andgit push --tags
.Prerequisites
brew install node
.npm install -g bower
.Initial publication to Bower
git tag v0.0.1 && git push --tags
.bower register typebetter https://github.com/yurivictor/typebetter.git
Initial publication to npm
npm adduser
and follow the prompts.npm publish .
That should publish to npm and you should see the package listed on your npmjs.com profile page.
You can test that this worked by running
bower install typebetter
andnpm install typebetter
in a test folder somewhere on your computer.Publishing subsequent releases
bower.json
andpackage.json
with the new version number (e.g. 0.0.2).git tag v0.0.2 && git push --tags
npm publish
from the root of the project. (Bower automatically picks up new releases based on git's tags.)Apologies if any of the above is repetitive, obvious, or otherwise unnecessary. I wanted to be overly thorough just in case. Happy to answer any questions or help out with any problems if they arise.