Puppeteer Core ESM TypeScript Build Config

TypeScript configuration for compiling Puppeteer Core to ESM format, extending base settings with custom output directory and third-party references.

n8n
Puppeteer Core ESM TypeScript Build Config

This workflow file, tsconfig.esm.json, is a specialized TypeScript configuration tailored for building the Puppeteer Core library in ECMAScript Module (ESM) format. It extends the base tsconfig.base.json from the project root, overrides the compiler options to direct output to '../lib/esm/puppeteer', and includes a reference to the third-party tsconfig.json for handling external dependencies. This setup ensures type-safe compilation optimized for modern ESM environments.

The benefits include streamlined build processes for Node.js developers working with Puppeteer, reducing compilation errors and enabling efficient browser automation scripting. It supports modular imports, improving code maintainability and tree-shaking for smaller bundles. Ideal for projects integrating headless Chrome automation in TypeScript/ESM setups.

Use cases span web scraping workflows in n8n, automated testing pipelines, PDF generation from web pages, and screenshot services. In language tools contexts, it powers dictionary or translation apps by automating browser interactions for dynamic content extraction. Developers can leverage this config in custom n8n nodes involving Puppeteer for robust, typed automation.

$3.99
Last updated November 14, 2026
30-day money-back guarantee
Instant download
Lifetime updates included

New buyers can create an account from the cart to unlock a controlled $10 first-purchase credit on eligible orders of $25+.

Secure checkout powered by Stripe

Support

How to import this workflow into n8n

  1. 1Purchase or download the workflow to get the n8n workflow JSON file.
  2. 2In your n8n instance, open Workflows and choose "Import from File" (or paste the JSON with Ctrl+V on the canvas).
  3. 3Open each node marked with a credential warning and connect your own accounts and API keys.
  4. 4Run the workflow once manually to verify the data flow, then toggle it to Active.

Related Language Tools workflows

More from BestWorkflows

Need this deployed? We'll set it up for you.

Our automation experts deploy this workflow in your stack, connect your accounts, and verify it works — or build a custom solution from scratch.