
Security News
Insecure Agents Podcast: Certified Patches, Supply Chain Security, and AI Agents
Socket CEO Feross Aboukhadijeh joins Insecure Agents to discuss CVE remediation and why supply chain attacks require a different security approach.
@botco/library
Advanced tools
Botco UI Components
run yarn storybook in a terminal
run yarn start in another
To be able to test our changes in any project, the first thing we must do is build the @botco/library library locally running in the root folder yarn build, after this have to run the following command yarn link (reference how this command works).
In the project that has @botco/library installed we must run yarn link "@botco/library" and then yarn install, to be able to link locally both repositories.
Going back to the @botco/library library in the root folder and run the command yarn start this will allow us to make changes in our code and that this is reflected immediately in the project which we have installed @botco/library.
@botco/library yarn build
yarn link
yarn start
@botco/{my_aweasome_project} yarn link "@botco/library"
yarn install
Once we are done with our changes, we must go back to the build folder and run yarn unlink and in the repository where @botco/library was implemented, we must run yarn install --force in order to restore this dependency and install it using npm again.
yarn unlink
yarn install --force
Making changes to the library components will automatically update Storybook, but to see those changes reflecting in the authoring-tool you need to restart the server with yarn start from any project using the library
To deploy storybooks to S3 instance run the next command npm run deploy-storybook.
aws installed and the aws botco account configured in it before run the command specified above.Clean up prettier rules to what we want Define TSLint rules to what we want Create real components
FAQs
Botco UI Components
The npm package @botco/library receives a total of 2 weekly downloads. As such, @botco/library popularity was classified as not popular.
We found that @botco/library demonstrated a not healthy version release cadence and project activity because the last version was released 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
Socket CEO Feross Aboukhadijeh joins Insecure Agents to discuss CVE remediation and why supply chain attacks require a different security approach.

Security News
Tailwind Labs laid off 75% of its engineering team after revenue dropped 80%, as LLMs redirect traffic away from documentation where developers discover paid products.

Security News
The planned feature introduces a review step before releases go live, following the Shai-Hulud attacks and a rocky migration off classic tokens that disrupted maintainer workflows.