v0.2.3
Features
-
Error if
package.json
has fields with invalid string, boolean, object, etc type (#73) -
Suggest using the
"files"
field if detected test or config files are published (#77) -
Warn on
"exports"
and"browser"
object conflict for browser-ish environments (#58)For example, given this setup:
{ "browser": { "./lib.server.js": "./lib.browser.js" }, "exports": { ".": { "worker": "./lib.server.js", "browser": "./lib.browser.js", "default": "./lib.server.js" } } }
When matching the
"worker"
condition, it will resolve to"./lib.server.js"
which is intended to work in a worker environment. However, the"browser"
field also has a matching mapping for"./lib.server.js"
, causing the final resolved path to be"./lib.browser.js"
. This is usually not intended and causes the wrong file to be loaded. -
Error on invalid JSX extensions, such as
.cjsx
,.mjsx
,.ctsx
, and.mtsx
(#76)These extensions are usually mistaken as ESM and CJS variants of JSX, which is not valid. Instead they should be written in ESM with the
.jsx
extension instead.
Bug fixes
- Skip file format checks only for globbed files
- Fix
"main"
field with ESM content detection (#75)
Site
- Add sidebar menu to rules page by @btea (#65)
- Quickly scroll to the prompt information location by @btea (#68)
- Fix version switch title not updated by @btea (#72)
- Improve documentation for
"types"
format - Fix message border styles
- Fix docs list missing dot
Full Changelog: v0.2.2...v0.2.3