botbuilder-core
Advanced tools
Readme
This library contains most of the core functionality for Bot Builder, but without any dependency on Node. As a result, this version can be used to build bots that run complete in a browser.
Unless you are building a bot or component without Node, we recommend that you botbuilder your app
instead of botbuilder-core. Learn more here.
To add the latset published version of this package to your bot:
npm install --save botbuilder-core
To get access to the daily builds of this library, configure npm to use the MyGet feed before installing.
npm config set registry https://botbuilder.myget.org/F/botbuilder-v4-js-daily/npm/
To reset the registry in order to get the latest published version, run:
npm config set registry https://registry.npmjs.org/
FAQs
Core components for Microsoft Bot Builder. Components in this library can run either in a browser or on the server.
The npm package botbuilder-core receives a total of 91,494 weekly downloads. As such, botbuilder-core popularity was classified as popular.
We found that botbuilder-core demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
A hospital in Mobile, Alabama, agreed to a settlement in a landmark ransomware death lawsuit, but is now reportedly reconsidering the agreement and refusing to pay.
Security News
A new report explores how advancements in LLMs are enhancing cyber threats, including polymorphic malware, personalized spearphishing, and the risk of hijacking customer service bots.
Security News
ESLint has approved an RFC that adds support for TypeScript configuration files, which is aimed at improving the developer experience and recognizing changes in the evolving JavaScript ecosystem.