{
  "@context": "https://schema.org",
  "@id": "https://aggr.aymericbeaumet.com/items/ampcode-com/2026-05-14-npm-package-changes/#webpage",
  "@type": [
    "WebPage",
    "ArchiveComponent"
  ],
  "articleBody": "We're now shipping the Amp CLI as a single-file executable ([compiled by Bun](https://bun.com/docs/bundler/executables)) instead of as a JavaScript source package. This makes Amp faster and more compatible across platforms and runtimes, and it's necessary to support [Amp plugins](https://ampcode.com/manual#plugins).\n\nIf you're using the recommended [direct installation](https://ampcode.com/manual#get-started), nothing changes for you. You've been using this single-file executable for several months. You can stop reading here.\n\nIf you've installed Amp via npm, you should switch to direct installation:\n\n```bash\nnpm uninstall -g @sourcegraph/amp\ncurl -fsSL https://ampcode.com/install.sh | bash\n```\n\n(See [all installation methods](https://ampcode.com/manual#get-started).)\n\nIf you need to keep using npm to install Amp, usually because your company has an internal npm mirror/archive, be aware of some changes:\n\n- The CLI's npm package will now contain the executable instead of sources.\n- We're renaming 2 npm packages:\n  - The Amp CLI is now [`@ampcode/cli`](https://www.npmjs.com/package/@ampcode/cli) (was [`@sourcegraph/amp`](https://www.npmjs.com/package/@sourcegraph/amp))\n  - The Amp TypeScript SDK is now [`@ampcode/sdk`](https://www.npmjs.com/package/@ampcode/sdk) (was [`@sourcegraph/amp-sdk`](https://www.npmjs.com/package/@sourcegraph/amp-sdk))\n\nThe old package names are aliases but will be removed on June 15, 2026.\n",
  "authors": [],
  "captured_at": "2026-10-03T23:09:50.514863041+00:00",
  "category": "programming",
  "content_html": "<p>We're now shipping the Amp CLI as a single-file executable (<a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://bun.com/docs/bundler/executables\">compiled by Bun</a>) instead of as a JavaScript source package. This makes Amp faster and more compatible across platforms and runtimes, and it's necessary to support <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://ampcode.com/manual#plugins\">Amp plugins</a>.</p>\n<p>If you're using the recommended <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://ampcode.com/manual#get-started\">direct installation</a>, nothing changes for you. You've been using this single-file executable for several months. You can stop reading here.</p>\n<p>If you've installed Amp via npm, you should switch to direct installation:</p>\n<pre><code class=\"language-bash\"><span class=\"code-snippet\" data-language=\"Shell\"><span class=\"syntax-source syntax-shell syntax-bash\"><span class=\"syntax-meta syntax-function-call syntax-shell\"><span class=\"syntax-variable syntax-function syntax-shell\">npm</span></span><span class=\"syntax-meta syntax-function-call syntax-arguments syntax-shell\"> uninstall<span class=\"syntax-variable syntax-parameter syntax-option syntax-shell\"><span class=\"syntax-punctuation syntax-definition syntax-parameter syntax-shell\"> -</span>g</span> @sourcegraph/amp</span>\n<span class=\"syntax-meta syntax-function-call syntax-shell\"><span class=\"syntax-variable syntax-function syntax-shell\">curl</span></span><span class=\"syntax-meta syntax-function-call syntax-arguments syntax-shell\"><span class=\"syntax-variable syntax-parameter syntax-option syntax-shell\"><span class=\"syntax-punctuation syntax-definition syntax-parameter syntax-shell\"> -</span>fsSL</span> https://ampcode.com/install.sh</span> <span class=\"syntax-keyword syntax-operator syntax-logical syntax-pipe syntax-shell\">|</span> <span class=\"syntax-meta syntax-function-call syntax-shell\"><span class=\"syntax-variable syntax-function syntax-shell\">bash</span></span>\n</span></span></code></pre>\n<p>(See <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://ampcode.com/manual#get-started\">all installation methods</a>.)</p>\n<p>If you need to keep using npm to install Amp, usually because your company has an internal npm mirror/archive, be aware of some changes:</p>\n<ul>\n<li>The CLI's npm package will now contain the executable instead of sources.</li>\n<li>We're renaming 2 npm packages:\n<ul>\n<li>The Amp CLI is now <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://www.npmjs.com/package/@ampcode/cli\"><code>@ampcode/cli</code></a> (was <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://www.npmjs.com/package/@sourcegraph/amp\"><code>@sourcegraph/amp</code></a>)</li>\n<li>The Amp TypeScript SDK is now <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://www.npmjs.com/package/@ampcode/sdk\"><code>@ampcode/sdk</code></a> (was <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://www.npmjs.com/package/@sourcegraph/amp-sdk\"><code>@sourcegraph/amp-sdk</code></a>)</li>\n</ul>\n</li>\n</ul>\n<p>The old package names are aliases but will be removed on June 15, 2026.</p>\n",
  "content_markdown": "We're now shipping the Amp CLI as a single-file executable ([compiled by Bun](https://bun.com/docs/bundler/executables)) instead of as a JavaScript source package. This makes Amp faster and more compatible across platforms and runtimes, and it's necessary to support [Amp plugins](https://ampcode.com/manual#plugins).\n\nIf you're using the recommended [direct installation](https://ampcode.com/manual#get-started), nothing changes for you. You've been using this single-file executable for several months. You can stop reading here.\n\nIf you've installed Amp via npm, you should switch to direct installation:\n\n```bash\nnpm uninstall -g @sourcegraph/amp\ncurl -fsSL https://ampcode.com/install.sh | bash\n```\n\n(See [all installation methods](https://ampcode.com/manual#get-started).)\n\nIf you need to keep using npm to install Amp, usually because your company has an internal npm mirror/archive, be aware of some changes:\n\n- The CLI's npm package will now contain the executable instead of sources.\n- We're renaming 2 npm packages:\n  - The Amp CLI is now [`@ampcode/cli`](https://www.npmjs.com/package/@ampcode/cli) (was [`@sourcegraph/amp`](https://www.npmjs.com/package/@sourcegraph/amp))\n  - The Amp TypeScript SDK is now [`@ampcode/sdk`](https://www.npmjs.com/package/@ampcode/sdk) (was [`@sourcegraph/amp-sdk`](https://www.npmjs.com/package/@sourcegraph/amp-sdk))\n\nThe old package names are aliases but will be removed on June 15, 2026.\n",
  "dateCreated": "2026-10-03T23:09:50.514863041+00:00",
  "date_created": "2026-05-14T00:00:00+00:00",
  "date_modified": "2026-05-14T00:00:00+00:00",
  "date_published": "2026-05-14T00:00:00+00:00",
  "description": "We're now shipping the Amp CLI as a single-file executable (compiled by Bun) instead of as a JavaScript source package. This makes Amp faster and more compatible across platforms and runtimes, and it's necessary to support Amp plugins. If…",
  "external_url": "https://ampcode.com/news/npm-package-changes",
  "git": {
    "commit": "ebb0941c5c06a2ab2377342d607535262a3e969e",
    "path": "items/ampcode-com/2026/05/2026-05-14-npm-package-changes.md",
    "permalink": "https://github.com/aymericbeaumet/aggr-instance/blob/ebb0941c5c06a2ab2377342d607535262a3e969e/items/ampcode-com/2026/05/2026-05-14-npm-package-changes.md"
  },
  "id": "urn:aggr:item:081190f9d939aeaca051b009f795f39819b98dc4",
  "isBasedOn": {
    "@id": "https://ampcode.com/news/npm-package-changes"
  },
  "mainEntity": {
    "@id": "https://ampcode.com/news/npm-package-changes",
    "@type": "CreativeWork",
    "archivedAt": {
      "@id": "https://aggr.aymericbeaumet.com/items/ampcode-com/2026-05-14-npm-package-changes/#webpage"
    },
    "dateModified": "2026-05-14T00:00:00+00:00",
    "datePublished": "2026-05-14T00:00:00+00:00",
    "headline": "npm Package Changes",
    "timeRequired": "PT1M",
    "url": "https://ampcode.com/news/npm-package-changes",
    "wordCount": 170
  },
  "name": "Archived snapshot: npm Package Changes",
  "preview": null,
  "reading_minutes": 1,
  "replicated_at": null,
  "source": "ampcode-com",
  "source_name": "Amp News",
  "summary": "We're now shipping the Amp CLI as a single-file executable (compiled by Bun) instead of as a JavaScript source package. This makes Amp faster and more compatible across platforms and runtimes, and it's necessary to support Amp plugins. If you're using the recommended direct installation, nothing changes for you. You've been using this single-file executable for several months. You can stop reading here. If you've installed Amp via npm, you should switch to direct installation: npm uninstall -g @sourcegraph/amp curl -fsSL https://ampcode.com/install.sh | bash (See all installation methods.) If you need to keep using npm to install Amp, usually because your company has an internal npm mirror/archive, be aware of some changes: The CLI's npm package will now contain the executable instead of sources. We're renaming 2 npm packages: The Amp CLI is now @ampcode/cli (was @sourcegraph/amp) The Amp TypeScript SDK is now @ampcode/sdk (was @sourcegraph/amp-sdk) The old package names are aliases but will be removed on June 15, 2026.",
  "tags": [],
  "temporalCoverage": "2026-10-03T23:09:50.514863041+00:00",
  "title": "npm Package Changes",
  "url": "https://aggr.aymericbeaumet.com/items/ampcode-com/2026-05-14-npm-package-changes/",
  "word_count": 170
}