@friendemic/catalyst-chat-widget v0.2.0-next.5

DISTRIBUTION

NOTE: public/index.html should be updated to reflect changes to snippet.html

See snippet.html for distribution snippet

TESTING A SPECIFIC VERSION

NOTE: Update the app_id value in snippet.html to override the production Application

• Update snippet.html URLs to use a specific npm version
• Update app_id to use the Staging enviornment

app_id: '70C5B4F2-A7CF-4BD6-81C4-68841DE927CC', // Staging

https://cdn.jsdelivr.net/npm/@friendemic/catalyst-chat-widget@1.2.3-next.4/build/static/css/main.css
https://cdn.jsdelivr.net/npm/@friendemic/catalyst-chat-widget@1.2.3-next.4/build/static/js/main.js

PUBLISHING

Acquire a valid .npmrc file for Friendemic.

Helpful commands:

# all-in-one patch and publish with automatic @latest tag
npm version patch && npm publish && git push && git push --tags

# reference for pre-versions: premajor | preminor | prepatch | prerelease
# IMPORTANT! publish with `--tag next`, or else version will have tag @latest
npm version preminor --preid=next # v0.1.0 => v0.2.0-next.0
npm version prerelease # v0.2.0-next.0 > v0.2.0-next.1
npm publish --tag next # IMPORTANT: without `--tag next` package will publish as @latest
npm version patch # v0.1.0-next.1=> v0.1.0 (when used to escape pre-release)
npm publish # escape pre-release and publish with @latest tag

Fixing accidental publish to @latest

npm unpublish <name>[@<version>]
npm unpublish @yourdomain/your_package@1.1.100
npm unpublish @friendemic/catalyst-chat-widget@1.2.3-next.4

Validating @latest version of package

Visit https://semver.npmjs.com/

• pick a package: @friendemic/catalyst-chat-widget
• enter a range: latest or next
  • range can be a semver identifier (like found in a package.json dependency) or a tag (latest, next, etc)