tw-plugin-rollup 1.0.0 → 1.0.2

package/README.md

@@ -196,7 +196,7 @@ Details:
 ## Notes & caveats
 
 - **One file only.** TurboWarp loads a single `<script>`, so don't use dynamic `import()` / code splitting — keep it one synchronous bundle. The plugin sets `output.inlineDynamicImports` to enforce a single chunk.
-- **`Scratch` is a global**, not an import. Your editor/linter may flag it; declare it as a readonly global (e.g. in ESLint `languageOptions.globals`). For TypeScript, [`@turbowarp/types`](https://github.com/TurboWarp/types) provides the `Scratch` typings.
+- **`Scratch` is a global**, not an import. Your editor/linter may flag it; declare it as a readonly global (e.g. in ESLint `languageOptions.globals`). For TypeScript, [`@turbowarp/types`](https://github.com/TurboWarp/types) provides the `Scratch` typings for **Scratch** extensions. If you're targeting **TurboWarp or one of its forks**, use [`types-tw`](https://github.com/TurboWarp/types-tw) instead, which adds the TurboWarp-specific APIs. It's no longer published to npm, so install it from git — it keeps the `@turbowarp/types` package name as a drop-in replacement: `npm install @turbowarp/types@git+https://github.com/TurboWarp/types-tw.git#tw`.
 - **Source maps:** prefer `sourcemap: false`. A trailing `//# sourceMappingURL=` comment would otherwise sit in the middle of the wrapped file. (When sourcemaps are on, the plugin uses `magic-string` to keep the mapping correct across the wrapper.)
 
 ## Is a plugin the best way to do this?

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "tw-plugin-rollup",
   "description": "Bundle a multi-file TurboWarp/Scratch extension into a single unsandboxed-extension file with Rollup, Rolldown, or Vite.",
-  "version": "1.0.0",
+  "version": "1.0.2",
   "type": "module",
   "license": "MPL-2.0",
   "author": "playforge-coding",