TS2309: An export assignment cannot be used in a module with other exported elements.

Steps to reproduce

Tell us about your environment:

• Puppeteer version: 7.0.4
• Platform / OS version: Windows 10
• Node.js version: v14.15.4

What steps will reproduce the problem? This started happening after updating from 7.0.1 to 7.0.4 1. tsconfig.json:

{
  "compilerOptions": {
    "target": "ESNext",
    "module": "ESNext",
    "outDir": "dist",
    "sourceMap": true,
    "moduleResolution": "node",
    "allowSyntheticDefaultImports": true
  }
}

main.ts:

import puppeteer from 'puppeteer';

(async () => {
  puppeteer.launch();
})();

1. run

tsc -p tsconfig.json

What is the expected result? Project should compile

What happens instead?

node_modules/puppeteer/lib/types.d.ts:24385:1 - error TS2309: An export assignment cannot be used in a module with other exported elements.

[jackfranklin]

Hey all,

I have learned a lot about shipping TS this week and we think v7.1.0 which shipped today fixes this. It no longer uses export = or export default in an attempt to be compat with your environment, regardless of if it’s ESM or CJS that you’re working with.

We also now automatically test our TS types against a tonne of environments: https://github.com/puppeteer/puppeteer/tree/main/test-ts-types, some use ESM, some CJS, etc, to try to avoid issues like this in the future.

I’m going to close this as I think 7.1.0 fixes it, but please open issues if you have problems, and I’m sorry for the churn and problems we’ve hit so far on this.

[tdodgehdai]

I’m having this issue too. Using @SimonHessel 's fix for now.