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.
@kaizen/package-bundler
Advanced tools
Bundles libraries
Bundle packages as CJS and ESM with TypeScript types.
ESM code is tree-shakeable.
pnpm add -D @kaizen/package-bundler
For shared UI packages, CSS modules and/or Tailwind will be included in the dist along side the components JS.
Note: styles are injected into the JS of components, so there's no need for consumers to manually import CSS files, it all comes with the component.
package.json
Add the following to your package.json
:
"main": "dist/cjs/index.cjs",
"module": "dist/esm/index.mjs",
"types": "dist/types/index.d.ts",
"files": [
"dist"
],
"sideEffects": [
"tailwind.css.*" // If using Tailwind
],
"scripts": {
"build": "pnpm package-bundler build-shared-ui",
}
pnpm add -D postcss postcss-preset-env rollup tslib
devDependencies
:
postcss
postcss-preset-env
rollup
tslib
(peerDep of rollup
)tailwind
postcss.config.js
rollup.config.(mjs|ts)
tsconfig.json
tsconfig.dist.json
tsconfig.types.json
tailwind.config.js
src/tailwind.css
In postcss.config.js
:
module.exports = {
plugins: {
"postcss-import": {},
cssnano: {},
},
}
If using Tailwind:
module.exports = {
plugins: {
"postcss-import": {},
"tailwindcss/nesting": "postcss-nesting",
tailwindcss: {},
autoprefixer: {},
cssnano: {},
},
}
In rollup.config.(mjs|ts)
:
import { pluginsSharedUi, rollupConfig } from "@kaizen/package-bundler";
export default rollupConfig({
// Add extra entrypoints as required
input: { index: "./src/index.ts" },
plugins: pluginsSharedUi,
})
// tsconfig.json
{
"extends": "@kaizen/package-bundler/tsconfig.base.json"
}
// tsconfig.dist.json
{
"extends": [
"./tsconfig.json",
"@kaizen/package-bundler/tsconfig.dist.json"
]
}
// tsconfig.types.json
{
"extends": [
"./tsconfig.dist.json",
"@kaizen/package-bundler/tsconfig.types.json"
]
}
pnpm add -D tailwind @kaizen/tailwind
Required files:
tailwind.config.js
src/tailwind.css
Follow the set up guide.
As we use PostCSS, ensure your postcss.config.js
has the following plugins installed:
module.exports = {
plugins: {
"postcss-import": {},
"tailwindcss/nesting": "postcss-nesting",
tailwindcss: {},
autoprefixer: {},
cssnano: {},
},
}
If you are creating a UI library to share with others, ensure you set a unique prefix to avoid clashes with other libraries.
// tailwind.config.js
module.exports = {
prefix: "{uniquePrefix}-"
}
You will also need to add the compiled Tailwind stylesheet to sideEffects
in your package.json
to ensure it is not tree-shaken:
"sideEffects": [
"tailwind.css.*"
]
If you are using aliases, ensure you have them listed in your tsconfig.json
(the tsconfig.dist
and tsconfig.types
should extend this) and in rollup.config
.
Example:
// tsconfig.json
{
"compilerOptions": {
"paths": {
"~components/*": ["./src/*"],
}
}
}
// tsconfig.dist.json
{
"extends": ["./tsconfig.json", "@kaizen/package-bundler/tsconfig.dist.json"],
}
// rollup.config.(mjs|ts)
export default rollupConfig({
alias: {
entries: [
{ find: "~components", replacement: "src" },
],
},
})
FAQs
Bundles libraries
We found that @kaizen/package-bundler demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 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.