semantic error TS2339: Property 'write' does not exist on type 'Clipboard' -- can't repro

[wamujlb]

What happens and why it is wrong

(rpt2 plugin) Error: ../...tsx(48,34): semantic error TS2339: Property 'write' does not exist on type 'Clipboard'.

I'm trying to use clipboard.write API but it throws an error on compilation.

Environment

Node 16

Versions

npmPackages:
    typescript: ^4.5.5 => 4.6.2
    rollup-plugin-typescript2: ^0.31.2

tsconfig.json

`tsconfig.json`:

{
  "compilerOptions": {
    "outDir": "dist",
    "module": "esnext",
    "target": "ESNext",
    "lib": ["dom", "esnext"],
    "moduleResolution": "node",
    "jsx": "react",
    "sourceMap": true,
    "declaration": true,
    "esModuleInterop": true,
    "downlevelIteration": true,
    "noImplicitReturns": true,
    "noImplicitThis": true,
    "noImplicitAny": true,
    "strictNullChecks": true,
    "suppressImplicitAnyIndexErrors": true,
    "noUnusedLocals": true,
    "noUnusedParameters": true,
    "allowSyntheticDefaultImports": true,
    "typeRoots": ["node_modules/@types", "src/lib-types"],
    "types": ["resize-observer-browser"]
  },
  "include": ["src", "scripts"],
  "exclude": ["node_modules", "dist", "example"],
  "paths": {
    "@src/*": ["./src/*"],
    "@types/*": ["./src/types"],
    "@components/*": ["./components/*"]
  }
}

[agilgur5]

Does tsc throw the same error or no?

[agilgur5]

You didn't provide a full code example, but if you mean the navigator.clipboard API, it appears that write was added to the DOM TS standard typings in microsoft/TypeScript#44842 and released along with TS 4.4 as far as I can tell.

So if tsc doesn't throw the same error, then I would think you may have a TS version mismatch and may need to pass the typescript option into this plugin.

Alternatively, you could also use @types/dom-clipboard-api

Per the MDN doc linked above, this seems to be a pretty new feature (writeText is a little older), and not fully supported or allowed on all browsers in all contexts.

[agilgur5]

I created a minimal reproduction here and was unable to reproduce this error.

Both tsc and rpt2 do not give this error in their latest versions (4.7.3 for TS, 0.32.1 for rpt2).

So the error you're getting is likely due to a problem in your environment, and not a bug in rpt2.