Configuration

Preconstruct accepts configuration at three different configuration points; projects, packages and entrypoints. These configuration points can be represented by one package.json or by 20 package.jsons, it depends on the requirements of a specific project. For example, in a single package repo with one entrypoint, it would be represented by a single package.json.

Projects map 1:1 with a version control repository. They specify global configuration that applies to all builds.

Projects

packages

Array<string>

packages is an array of globs which specify which packages should be built with preconstruct.

Default

Note: this is the default value, if it's what you want, you don't need to specify it.

{
  "preconstruct": {
    "packages": ["."]
  }
}

Example

{
  "preconstruct": {
    "packages": ["packages/*"]
  }
}

globals

{ [packageName: string]: (umdName: string) }

globals specifies the UMD names of peerDependencies since peerDependencies aren't bundled in UMD builds. You shouldn't specify this option manually, preconstruct will prompt you for the UMD name of a package when it's necessary.

Default

Note: this is the default value, if it's what you want, you don't need to specify it.

{
  "preconstruct": {
    "globals": {}
  }
}

Example

{
  "preconstruct": {
    "globals": {
      "react": "React",
      "react-dom": "ReactDOM"
    }
  }
}

distFilenameStrategy

"full" | "unscoped-package-name"

distFilenameStrategy specifies, you should probably use full(which is the default) unless you need to have filenames (likely if you have UMD builds whose filename you don't want to change) in which case, you should use unscoped-package-name

Entrypoint	full	unscoped-package-name
pkg	dist/pkg.cjs.js	dist/pkg.cjs.js
pkg/entrypoint	dist/pkg-entrypoint.cjs.js	dist/pkg.cjs.js
@scope/pkg	dist/scope-pkg.cjs.js	dist/pkg.cjs.js
@scope/pkg/entrypoint	dist/scope-pkg-entrypoint.cjs.js	dist/pkg.cjs.js

Default

Note: this is the default value, if it's what you want, you don't need to specify it.

{
  "preconstruct": {
    "distFilenameStrategy": "full"
  }
}

Example

{
  "preconstruct": {
    "distFilenameStrategy": "unscoped-package-name"
  }
}

Packages

Packages map 1:1 with npm packages. Along with specifying the entrypoints option described below, packages are also responsible for specifying dependencies which is necessary for bundling UMD bundles and ensuring that packages will have all of their required dependencies when installed through npm.

entrypoints

Array<string>

entrypoints is an array of globs which specify the entrypoints which consumers of your package should be able to import. They are resolved relative to the src directory of the package. To get the entrypoint directory from a source file, the extension is removed from the path relative to the src directory and if the last part is index, the index part is removed. For example, an entrypoint of something.js would create an entrypoint at pkg-name/something and another/index.js would create an entrypoint at pkg-name/another.

Default

Note: this is the default value, if it's what you want, you don't need to specify it.

{
  "preconstruct": {
    "entrypoints": ["index.{js,jsx,ts,tsx}"]
  }
}

Example

{
  "preconstruct": {
    "entrypoints": ["index.js", "other.js"]
  }
}

exports

| boolean
| {
    envConditions?: ("browser" | "worker")[];
    extra?: Record<string, JSONValue>;
  };

The exports config allows you to opt-in to generating an exports field.

Using the exports field enables a couple of things:

• Importing non-root entrypoints in Node.js ESM
• Disallowing importing modules that aren't specified in the exports field
• More specific builds for certain environments

Note that Preconstruct's support for the exports field does not currently include generating ESM compatible with Node.js. While ESM builds are generated, they are targeting bundlers, not Node.js or browsers directly so they use the module condition, not the import condition.

Note that adding an exports field can arguably be a breaking change, you may want to use the extra option to add more exports so that imports that worked previously still work or only add the exports field in a major version.

The exports field feature can be enabled at the project or package level like this. The envConditions and extra options can only be configured at the package level. The importConditionDefaultExport option can be configured at the project or package level.

{
  "name": "@sample/package",
  "version": "1.0.0",
  "preconstruct": {
+   "exports": true
  }
}

envConditions

Array<"browser" | "worker">

Specifying the envConditions option adds additional environments that Preconstruct will generate bundles for. This option is currently aimed at generating bundles with typeof SOME_ENV_SPECIFIC_GLOBAL replaced with what it would be in that environment. It may be expanded to provide the ability to have Preconstruct resolve a different file or etc. depending on the environment in the future.

Builds

• browser: Generates a bundle targeting browsers. When this condition is used, the top-level browser field will also be set so that older bundlers that do not understand the exports field will be able to use the browser build (though when using the exports field, browser CommonJS builds will not be built). When building with this condition, typeof document and typeof window will be replaced with "object" and dead-code elimination will occur based on that.
• worker: Generates a bundle targeting web workers/server-side JS runtimes that use web APIs. When building with this condition, typeof document and typeof window will be replaced with "undefined" and dead-code elimination will occur based on that.

{
  "name": "@sample/package",
  "version": "1.0.0",
  "preconstruct": {
    "exports": {
      "envConditions": ["browser", "worker"]
    }
  }
}

extra

Record<string, JSONValue>

Preconstruct will enforce that the exports field that is written can is directly a function of your config, this means that extra properties are not allowed to be written directly in the exports field. If you want to add extra entries to the exports field, you can use the extra option in preconstruct.exports and then preconstruct fix will add add them to the actual exports field.

{
  "name": "@sample/package",
  "version": "1.0.0",
  "preconstruct": {
    "exports": {
      "extra": {
        "./something": "./something.js"
      }
    }
  }
}

importConditionDefaultExport

"namespace" | "default"

Preconstruct doesn't generate bundles targeting Node ESM to avoid the dual package hazard. Instead of generating a bundle for Node ESM, the CommonJS bundle is used in Node ESM and because of Node's usage of cjs-module-lexer, importing named exports from CommonJS packages works correctly. Default exports are more complicated though. The way that Preconstruct and many other tools generate CommonJS bundles is like this.

export default "a";

↓

"use strict";

Object.defineProperty(exports, "__esModule", { value: true });

var main = "a";

exports.default = main;

And for compiling importing a default export from a CommonJS module like this,

import a from "a";

console.log(a);

↓

"use strict";

var x = require("b");

function _interopDefault(e) {
  return e && e.__esModule ? e : { default: e };
}

var x__default = /*#__PURE__*/ _interopDefault(x);

console.log(x__default.default);

however, Node doesn't look at the __esModule convention to get the default export of a CommonJS module when importing in ESM. Instead, it uses the whole module.exports object as the default export.

This means running b.mjs here would log { default: "a", __esModule: true } instead of "a".

// a.cjs
"use strict";

Object.defineProperty(exports, "__esModule", { value: true });

var main = "a";

exports.default = main;

// b.mjs
import a from "./a.cjs";

console.log(a);

To get around this, you can set preconstruct.exports.importConditionDefaultExport to "default" which will make Preconstruct generate a ESM module for Node that re-exports the CommonJS bundle with the correct default export.

Currently, this defaults to "namespace", this will change to "default" in the next major version.

{
  "name": "@sample/package",
  "version": "1.0.0",
  "preconstruct": {
    "exports": {
      "importConditionDefaultExport": "default"
    }
  }
}

Entrypoints

Entrypoints are the lowest level configuration point and describe a set of bundles for a particular entrypoint. They are configured by the package.json in the folder of the entrypoint. We also have a guide on adding a second entrypoint

Build types

Build types specify what types of bundles Preconstruct should build. They are specified via the package.json fields which Node and bundlers like webpack look at to find bundles. It's important to note that all of the entrypoints in a package must have the same build types, this is necessary to ensure that common dependencies between entrypoints aren't duplicated.

main

The main field specifies a CommonJS build. It is the only build type which is required. This bundle will work in Node and can work in bundlers like webpack but a ES Module build is recommended for bundlers like webpack.

Example:

{
  "main": "dist/my-package.cjs.js"
}

Note: This file actually just reexports either a production or a development bundle (respectively dist/my-package.cjs.prod.js or dist/my-package.cjs.dev.js in this example) based on the process.env.NODE_ENV value. This allows you to use process.env.NODE_ENV checks in your code so 2 distinct bundles are created but at runtime only one of them gets loaded.

module

The module field specifies an ES Module build. This bundle is what bundlers like webpack will use.

Example:

{
  "module": "dist/my-package.esm.js"
}

umd:main

The umd:main field specifies a UMD build. This bundle can be used directly in a browser with a <script> tag.

Example:

{
  "umd:main": "dist/my-package.umd.min.js"
}

browser

The browser field specifies alias files exclusive to browsers. This allows you to create different bundles from your source code based on typeof window and typeof document checks - thanks to that you can, for example, remove server-only code (just for those bundles).

Note: Those files are not meant to be consumed by browsers "as is". They just assume browser-like environment, but they still can contain for example references to process.env.NODE_ENV as that is meant to be replaced by a consuming bundler.