Add npm keywords to all packages for improved discoverability
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
## Summary
Added relevant npm keywords to all 7 published packages to improve discoverability on npmjs.com.
## Problem
None of the radpack packages include the `keywords` field in their `package.json`. This significantly hurts discoverability when developers search for webpack plugins, rollup plugins, module loaders, SSR solutions, or code-splitting libraries on npm.
## Solution
Added carefully selected keywords to each package based on their actual functionality:
- **@radpack/core**: `module-loader`, `dynamic-import`, `code-splitting`, `runtime`, `amd`, `graph-based-loading`, `dependency-graph`, `resource-sharing`
- **@radpack/client**: `browser`, `client`, `runtime`, `module-loader`, `dynamic-import`, `amd`, `lazy-loading`, `code-splitting`, `frontend`
- **@radpack/server**: `server`, `ssr`, `server-side-rendering`, `node`, `runtime`, `module-loader`, `middleware`, `hydration`, `isomorphic`
- **@radpack/build**: `build`, `bundler`, `webpack`, `rollup`, `manifest`, `registry`, `exports`, `semver`, `build-tool`
- **@radpack/rollup-plugin**: `rollup`, `rollup-plugin`, `library`, `esm`, `build-tool`, `shared-dependencies`, `module-loader`
- **@radpack/webpack-plugin**: `webpack`, `webpack-plugin`, `webpack4`, `webpack5`, `application`, `code-splitting`, `build-tool`, `dynamic-import`, `resource-sharing`
- **@radpack/cli**: `cli`, `command-line`, `dev-server`, `local-server`, `registry`, `merge`, `development`
## Impact
- ✅ Improved npm search ranking for relevant queries
- ✅ Better package discovery for potential users
- ✅ Increased organic traffic to package pages
- ✅ Non-breaking metadata-only change
## Files Changed
All 7 package.json files in `packages/*/packag
Contributor guide
Assessment
This issue has not been assessed yet.