
Security News
Risky Biz Podcast: Making Reachability Analysis Work in Real-World Codebases
This episode explores the hard problem of reachability analysis, from static analysis limits to handling dynamic languages and massive dependency trees.
@pinnacle0/webpack-util
Advanced tools
This project is to provide two helpers, based on `webpack`:
This project is to provide two helpers, based on webpack
:
Following Convention Over Configuration
,
we provide two all-in-one tools for webpack development and build.
WebpackServerStarter
new WebpackServerStarter({
projectDirectory: path.join(import.meta.dirname, ".."),
port: 1234,
}).run();
webpack
compiler instance (development mode) and runs it with webpack-dev-server
.localhost
https server in 1234
port.WebpackBuilder
new WebpackBuilder({
projectDirectory: path.join(import.meta.dirname, ".."),
}).run();
prettier
/ stylelint
/ eslint
rules.package.json
scripts.webpack
compiler instance (production mode) and bundle into an index.html
with related CSS/JS/images etc.TypeScript/JavaScript
CSS/LESS
eslint
stylelint
prettier
Note: CSS/LESS only website also supported, without any JavaScript.
The following structure can be used for a basic project setup.
<projectDirectory>
├── build/
│ └── dist/
│ (Output directory for build artifacts, content will be
│ overwritten by each build, should be ignored by git)
├── src/
│ ├── index.html
│ │ (HTML entry)
│ └── index.{ts,tsx,js,jsx,less,css}
│ (Main entry)
├── static/
│ (Directory to serve static files, e.g: robots.txt)
├── tsconfig.json
│ (TypeScript config)
├── .eslintrc.js
│ (ESLint config, can be moved to upper directories)
├── prettier.config.js
│ (Prettier config, can be moved to upper directories)
├── stylelint.config.js
│ (Stylelint config, can be moved to upper directories)
└── package.json
(Project manifest file)
The following structure can be used for a npm/yarn/pnpm workspace setup.
<workspaceRootDirectory>
├── packages/
│ ├── project1/
│ │ ├── build/dist/
│ │ ├── config/
│ │ │ ├── tsconfig.script.json (extends: "../../../tsconfig.base.json", ...)
│ │ │ ├── tsconfig.src.json (extends: "../../../tsconfig.base.json", ...)
│ │ │ └── tsconfig.test.json (extends: "../../../tsconfig.base.json", ...)
│ │ ├── script/
│ │ │ ├── build.ts
│ │ │ └── start.ts
│ │ ├── src/
│ │ │ ├── index.html
│ │ │ └── index.{ts,tsx,js,jsx,less,css}
│ │ ├── static/
│ │ ├── tsconfig.json (files: [], references: [{path: "config/tsconfig.src.json"}, ...])
│ │ └── package.json
│ └── project2/
│ ├── build/dist/
│ ├── config/
│ │ ├── tsconfig.script.json (extends: "../../../tsconfig.base.json", ...)
│ │ ├── tsconfig.src.json (extends: "../../../tsconfig.base.json", ...)
│ │ └── tsconfig.test.json (extends: "../../../tsconfig.base.json", ...)
│ ├── script/
│ │ ├── build.ts
│ │ └── start.ts
│ ├── src/
│ │ ├── index.html
│ │ └── index.{ts,tsx,js,jsx,less,css}
│ ├── static/
│ ├── tsconfig.json (files: [], references: [{path: "config/tsconfig.src.json"}, ...])
│ └── package.json
├── tsconfig.base.json (Define common options to be extended by other tsconfig files)
├── .eslintrc.js
├── prettier.config.js
├── stylelint.config.js
└── package.json
FAQs
This project is to provide two helpers, based on `webpack`:
The npm package @pinnacle0/webpack-util receives a total of 7 weekly downloads. As such, @pinnacle0/webpack-util popularity was classified as not popular.
We found that @pinnacle0/webpack-util demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 4 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
This episode explores the hard problem of reachability analysis, from static analysis limits to handling dynamic languages and massive dependency trees.
Security News
/Research
Malicious Nx npm versions stole secrets and wallet info using AI CLI tools; Socket’s AI scanner detected the supply chain attack and flagged the malware.
Security News
CISA’s 2025 draft SBOM guidance adds new fields like hashes, licenses, and tool metadata to make software inventories more actionable.