Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
@storybook/preact-vite
Advanced tools
Storybook for Preact and Vite: Develop Preact components in isolation with Hot Reloading.
Follow the prompts after running this command in your Preact project's root directory:
npx storybook@latest init
More on getting started with Storybook
This framework is designed to work with Storybook 7. If you’re not already using v7, upgrade with this command:
npx storybook@latest upgrade
Install the framework:
yarn add --dev @storybook/preact-vite
Update your main.js
to change the framework property:
// .storybook/main.js
export default {
// ...
framework: {
name: '@storybook/preact-vite', // <- Change this
options: {},
},
};
FAQs
Storybook for Preact and Vite: Develop Preact components in isolation with Hot Reloading.
The npm package @storybook/preact-vite receives a total of 12,848 weekly downloads. As such, @storybook/preact-vite popularity was classified as popular.
We found that @storybook/preact-vite demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 12 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
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.