@preconstruct/cli@2.2.2

Patch Changes

• #495 4e90c2b Thanks @mycroes! - The outDir and declarationDir tsconfig options are now ignored. These options are unnecessary for Preconstruct since it controls where the .d.ts files are emitted to. This fixes confusing errors if you had these options set.

• eaa2fcc Thanks @mitchellhamilton! - Improved error when importing something with an extension that can't be imported

@preconstruct/cli@2.2.1

Patch Changes

• #476 3930466 Thanks @mitchellhamilton! - Using node: to import Node builtins no longer triggers a "package is not specified in dependencies or peerDependencies" error

• #481 76f0163 Thanks @efoken! - Updated @rollup/plugin-node-resolve to ^11.2.1 in order to make direct imports resolveable, e.g. packages that use exports in their package.json

@preconstruct/cli@2.2.0

Minor Changes

• #474 a05414d Thanks @mitchellhamilton! - .d.ts files can now be written next to .js entrypoints and they will be appropriately written to the dist.

@preconstruct/cli@2.1.8

Patch Changes

• #435 014038b Thanks @nicksrandall! - Added experimental exports flag. See the docs at the exports section of https://preconstruct.tools/configuration.

@preconstruct/cli@2.1.7

Patch Changes

• 3f202fd Thanks @mitchellhamilton! - Imports to @babel/runtime/helpers/esm/* will now be rewritten to @babel/runtime/helpers/* for CommonJS outputs. This fixes the CommonJS output in case you have ["@babel/plugin-transform-runtime", { "useESModules": true }]) in your Babel config.

@preconstruct/cli@2.1.6

Patch Changes

• #461 97e7ca0 Thanks @simonswiss! - Fixed grammar in CLI info message about errors

• f6f2e60 Thanks @mitchellhamilton! - Fixed bigint usage causing an error

@preconstruct/next@4.0.0

Major Changes

• 8b740fe Thanks @mitchellhamilton! - @preconstruct/next now makes Next.js prefer the module field over the main for server-side bundles. This is different to the behaviour that Next.js provides by default, for that reason, this change is happening in a major release of @preconstruct/next. The module field is generally regarded by most package authors and tools like Preconstruct to only indicate module format and not Node vs browser. This resolves issues with using preconstruct dev with packages that have dependencies that ship Node ESM(in addition to CommonJS).

@preconstruct/eslint-plugin-format-js-tag@0.2.0

Minor Changes

• #422 074bae7 Thanks @gwyneplaine! - Support ESLint 8

@preconstruct/next@3.0.1

Patch Changes

• #420 9fc0cf5 Thanks @bradbarrow! - Fixed support for Next.js 12. Note that in Next.js 11 and 12, Next will not read a Babel config from outside of the directory that the Next.js site is in. If you need it to to read your babel config, you will need to do something like this:

  // site/babel.config.js
  module.exports = require("../babel.config");

@preconstruct/cli@2.1.5

Patch Changes

• ad15ffa Thanks @mitchellhamilton! - Fixed resolving typescript package when using Yarn PnP and installing typescript at the root of a project