rolldown 1.x
Use Rolldown 1.x programmatically, with the current JavaScript API shape, standalone transform utilities, and correct bundle/plugin lifecycle handling.
- For
rolldown@1.2.7- Verified
- 2026-09-08, 2 examples executed
- Package
@modootoday/pmcp-rolldown@1.0.0
What it covers
- Scope
- Current JavaScript API shape
- The common old-API mistake
- Standalone transform utility
- Watch mode
- Bundle lifecycle and plugins
- Configuration and CLI boundaries
- Version-transition notes
- What this skill does not cover
One example from this skill
This is the skill's own text, not a summary of it. It runs: that is what verifying means here.
import assert from 'node:assert/strict';
import { defineConfig } from 'rolldown';
const config = defineConfig({
input: 'src/main.js',
output: { file: 'bundle.js' },
});
assert.equal(config.input, 'src/main.js');
assert.deepEqual(config.output, { file: 'bundle.js' });
What it did in the sandbox
Verifying this skill meant installing the package and running code against it with no route out. Nothing was observed. The full ledger lists every package examined, including the ones that never became a skill.
Nothing observed is not a finding of safety. It means one run, under one policy, produced nothing to report.
Getting it
With a subscription:
npx -y @modootoday/pmcp login
npx -y @modootoday/pmcp install @modootoday/pmcp-rolldown
It installs as a dev dependency of your project, and the MCP server finds it there like any other skill.