Skip to content

Latest commit

 

History

History
53 lines (41 loc) · 2.21 KB

DEVELOPMENT.md

File metadata and controls

53 lines (41 loc) · 2.21 KB

Developing Ember Fontawesome

Tasks

The following commands are available through npm run

Command Purpose
build Build this project
lint Check linting using ESLint
start Starts the addon and the test app
test Test all supported versions

Releasing a new version

See authenticating with the npm.fontawesome.com registry before doing the following

  1. Check if all CI tests on github 3.x branch were passed
  2. Open package.json from ember-fontawesome folder and update the version number
  3. Add new contributors to the contributors section
  4. Update the CHANGELOG.md
  5. pnpm install, run pnpm build and pnpm lint
  6. git add . && git commit -m 'Release VERSION'
  7. git push
  8. git tag 3.0.0 (update 3.0.0 always to released version number)
  9. git push origin 3.0.0 (update 3.0.0 always to released version number)
  10. cd ember-fontawesome
  11. pnpm publish --tag latest
  12. pnpm dist-tag add @fortawesome/[email protected] latest-3 (update 3.0.0 always to released version number)
  13. pnpm publish --tag latest --registry https://npm.fontawesome.com (publish to Pro registry)
  14. pnpm dist-tag add @fortawesome/[email protected] latest-3 --registry https://npm.fontawesome.com (update 3.0.0 always to released version number, push to Pro registry)
  15. Create a new release with CHANGELOG details

Authenticating with the npm.fontawesome.com registry

Contributors with authorization to publish to npm.fontawesome.com will receive an invite from a Font Awesome project owner.

  1. Respond to the invite in your email
  2. Let the owner know when you've setup your account
  3. Owner will add you to the team

You can then run:

npm login --registry https://npm.fontawesome.com
  • The username is the "slug" for your Cloudsmith account. For example mine is "rob-madole".
  • Enter password (it's the API Key, which you will find under API Settings)
  • It says the your email is PUBLIC. Pretty sure that's false since the auth is through Cloudsmith.
  • This doesn't overwrite your standard login, just adds to your ~/.npmrc