publint@0.3.21

Patch Changes

• Suggest adding "sideEffects": false when bundler-oriented package fields or conditions are detected and the field is missing. (#228)

publint@0.3.20

Patch Changes

• Suggest adding engines.node when it is missing from detected Node.js packages (#226)

• Loosen "breaking change" wording in lint messages (7bb3f4f)

publint@0.3.19

Patch Changes

• Add NESTED_PACKAGE_JSON_FIELD_IGNORED to warn when published nested package.json files define "exports" or "imports", which Node.js ignores outside the package root. (#224)

• Fix internal browser directory traversal logic (#224)

publint@0.3.18

Patch Changes

• Fix deprecated subpath mapping check crash and make getPkgPathValue from publint/utils return undefined if the path is invalid (ad2aa9c)

@publint/pack@0.1.4

Patch Changes

• Allow passing Uint8Array in unpack() (30016ac)

publint@0.3.17

Patch Changes

• Fix packing packages with pnpm when publishConfig.directory is set (#216)

• Updated dependencies [2dcb107]:

  • @publint/pack@0.1.3

@publint/pack@0.1.3

Patch Changes

• Add new getPackDirectory() API to get the directory that is being packed by the package manager (#216)

publint@0.3.16

Patch Changes

• Re-enable file existence checks for TS and TSX files if they do not use custom conditions. In v0.3.10, this was done unconditionally instead which missed catching possible file typos if only common conditions are used. (7b1408e)

publint@0.3.15

Patch Changes

• Skip file existence checks when crawling subpath imports as they may be dev-only and not used after bundling or publish. This check may be improved in the future when publint can scan for files to see if the subpath imports are used. (0d72997)

• Handle exports["default"] and exports['default'] for CJS_WITH_ESMODULE_DEFAULT_EXPORT rule (8285f77)

publint@0.3.14

Patch Changes

• Add a new warning when an entrypoint is exported as CJS-only, has a default export, and has the __esModule marker. This setup has different interpretations by bundlers and runtimes, and implicit handling detection that may not be obvious for both package authors and users, hence it is discouraged. (#201)