Chokidar TS

A thin wrapper on top of chokidar file watcher that relies on the tsconfig.json file to distinguish between the TypeScript source files and other files.

Why does this package exists?

When running a Node.js backend development server with a file watcher, we need to know whether a newly added or changed file is part of our TypeScript project.

The best way to establish if a file is part of a TypeScript project is to rely on the tsconfig.json file.

This is precisely what this package does. It will create a file watcher using chokidar and then uses the includes and excludes patterns from the tsconfig.json file to know if a changed file is part of a TypeScript project.

Setup

Install the package from the npm packages registry. In addition, the package has a peer dependency on the typescript package, so make sure to install that as well.

1npm i @poppinss/chokidar-ts

1yarn add @poppinss/chokidar-ts

1pnpm add @poppinss/chokidar-ts

And use it as follows.

1import typescript from 'typescript'
2import { ConfigParser, Watcher } from '@poppinss/chokidar-ts'
3
4const projectRoot = new URL('./', import.meta.url)
5const configFileName = 'tsconfig.json'
6
7const { config } = new ConfigParser(
8  projectRoot,
9  configFileName,
10  typescript,
11).parse()
12
13if (config) {
14  const watcher = new Watcher(projectRoot, config)
15  watcher.watch(['.'])
16}

Listening for events

The Watcher class emits the following events. Events prefixed with source refers to files included by the tsconfig.json file, and other events refer to non-typescript or files excluded by the tsconfig.json file.

• add: A new file has been added. The file is either not a TypeScript file or is excluded by the tsconfig.json file.
• source:add: A new TypeScript source file has been added.
• change: An existing file has been updated. The file is either not a TypeScript file or is excluded by the tsconfig.json file.
• source:change: An existing TypeScript source file has been changed.
• unlink: An existing file has been deleted. The file is not a TypeScript source file.
• source:unlink: An existing TypeScript source file has been deleted.

1const watcher = new Watcher(projectRoot, config)
2
3watcher.on('add', (file) => {
4  console.log(file.absPath)
5  console.log(file.relativePath)
6})
7
8watcher.on('source:add', (file) => {
9  console.log(file.absPath)
10  console.log(file.relativePath)
11})
12
13watcher.on('change', (file) => {
14  console.log(file.absPath)
15  console.log(file.relativePath)
16})
17
18watcher.on('source:change', (file) => {
19  console.log(file.absPath)
20  console.log(file.relativePath)
21})
22
23watcher.on('unlink', (file) => {
24  console.log(file.absPath)
25  console.log(file.relativePath)
26})
27
28watcher.on('source:unlink', (file) => {
29  console.log(file.absPath)
30  console.log(file.relativePath)
31})
32
33watcher.watch(['.'])

Handling config parser errors

Parsing the tsconfig.json file can produce errors, and you can display them using the TypeScript compiler as follows.

1import typescript from 'typescript'
2const { error, config } = new ConfigParser(
3  projectRoot,
4  configFileName,
5  typescript,
6).parse()
7
8if (error) {
9  const compilerHost = typescript.createCompilerHost({})
10  console.log(
11    typescript.formatDiagnosticsWithColorAndContext([error], compilerHost)
12  )
13
14  return
15}
16
17if (!config) {
18  return
19}
20
21if (config.errors) {
22  const compilerHost = typescript.createCompilerHost({})
23  console.log(
24    typescript.formatDiagnosticsWithColorAndContext(config.errors, compilerHost)
25  )
26
27  return
28}