Feature Request

And optionally, deprecate master dist-tag.

Package history

Package history at MyGet.

.npmrc

registry=https://botbuilder.myget.org/F/botframework-webchat/npm/

Rough draft

To use dev build,

1. Create/modify .npmrc locally and set registry
2. Run npm install botframework-webchat --save
3. Remove your changes in step 1 to reduce impact on your `package-lock.

@corinagum please verify these steps with a few things.

1. Look at package-lcok.json to make sure we have minimal impact
2. Remove node_modules, keep package-lock.json, then do npm install again
   • This mimic what the user would do on a fresh clone
   • Make sure npm install is grabbing the right version by drilling into node_modules folder seeing the package.json file inside
3. Same as step 2, but instead of npm install, run npm ci
   • Should be the same
4. Wirte up guides to reverse it back to production version
   1. (I didn't try the following steps)
   2. Run npm install botframework-webchat --save
   3. Make sure everything in package-lock.json is pointing to npmjs.org, and not a single package is point to myget.org
   4. Make sure it grab the 4.4.1 (production, not dev build)
      • Drill into node_modules folder to see
      • Don't forget to look at botframework-webchat-core and other packages
   5. Find the string "myget.org" in package-lock.json, make sure no package is affected if the user reverted, super important