jest-dev-server - npm Package Versions

8.0.0 (2023-03-06)

Features

• native typings (32acec7)

BREAKING CHANGES

• • spawnd now exports { spawd } instead of default to ensure compatibilty with ESM

• toMatch has been renamed toMatchTextContent to avoid collision with existing Jest matcher

7.0.1 (2023-02-15)

Bug Fixes

• jest-dev-server: fix port detection (#518) (805819d), closes #460 #281 #233

7.0.0 (2023-02-03)

Features

• modernize project (#514) (6ca8757)
• target puppeteer v19+ (31f6f1e)

BREAKING CHANGES

• requires puppeteer v19+

6.2.0 (2022-12-11)

Bug Fixes

• update deps (#508) (67701a7)

Features

• Add option runBeforeUnloadOnClose (#504) (317ed12)

6.1.1 (2022-07-06)

Bug Fixes

• expect-puppeteer: return proper error stack traces from matchers (#487) (e9cafb1)
• prevent stdout buffer from filling up (#482) (6f16345)

6.0.3 (2021-12-14)

Bug Fixes

• avoid running connect in global setup if browserWSEndpoint provided in config (#458) (c9fa515)

6.0.2 (2021-11-25)

Bug Fixes

• Revert catch on disconnect (#456) (51b8706)
• update deps (#457) (bcd0415)

6.0.0 (2021-09-23)

Bug Fixes

• Add browserPerWorker setting (#420) (5320871)
• allow puppeteer >= 1.5.0 (#442) (181ee72)
• only throw timed out error if timed out (#435) (f6c20ab)
• remove wait-port dependency (#434) (3d6cae0)

BREAKING CHANGES

• drop support for node v10

5.0.3 (2021-04-28)

Bug Fixes

• fix toFill on textarea (#399) (7f40bd7)
• update deps (#402) (fa91027)
• use Delete to clear input instead of Backspace (#401) (94e9241)

5.0.0 (2021-04-16)

Bug Fixes

• Leverage Puppeteer's native support for Firefox (#356) (e54fb7e)
• require to puppeteer-core as fallback (#315) (49d313c)
• Resolve module paths in preset (#335) (36602a1)
• toFill doesn't empty contents when given an empty string (#381) (964b9a2)

Features

• allow path for wait-on resource (#382) (f2f5b62)
• support XPATH selectors (#321) (949027b)

BREAKING CHANGES

• browser config is deprecated. Use launch.product instead.
• jest-dev-server uses axios instead of request so the waitOnScheme options may have changed. see wait-on v5.0.0 changelog for more details