Skip to content

Tags: caneroner/zombie

Tags

v4.0.10

Toggle v4.0.10's commit message
Upgraded to JSDOM 5.2.0 and tough-cookie 1.1.0

 694 passing (22s)
  12 pending

v4.0.9

Toggle v4.0.9's commit message
Upgraded to JSDOM 5.1.0

FIXED assertion errors not propagating our of wait callback

 694 passing (22s)
  12 pending

v4.0.8

Toggle v4.0.8's commit message
Upgraded to JSDOM 5.0.1

ADDED expose Browser.Request/Response/Headers

CHANGED use regexp instead of startsWith

 694 passing (22s)
  12 pending

v4.0.7

Toggle v4.0.7's commit message
Version 4.0 requires io.js, see:

https://github.com/tmpvar/jsdom/blob/master/Changelog.md#400

ADDED preliminary support for the Fetch API (https://fetch.spec.whatwg.org/)

ADDED you can use the `browser.fetch` to retrieve any resources, using the
cookies, pipeline and all other browser settings

CHANGED upgraded to JSDOM 4.1

CHANGED use `browser.status` instead of `browser.statusCode` (HTML APIs use
`status` and `statusText`)

CHANGED `browser.resources` is now just an array of all resources requested when
processing the currently open window.  Resources no longer shared by all
windows, and other features (pipeline configuration, fetch resources) moved
elsewhere.

CHANGED separated pipeline from resources.  Use `browser.pipeline.addHandler` to
add request/response handler to the browser instance, or `Pipeline.addHandler`
to add handler to all new instances.

CHANGED pipeline API changed as well.  Request handler called with browser
instance and Fetch `Request` object, can return null or a Fetch `Response`
object.  Response handler called with browser instance, request and response
object, should return same or new response object.  Handlers no longer using
callbacks, if you need asynchronous behavior, return a promise.

FIXED empty `cookie` and `referer` header no longer sent assaf#881

FIXED added `navigator.appVersion` assaf#885

REMOVED `document.window`, use `document.defaultView` instead

REMOVED `browser.close` confusing method name, use `browser.window.close` if you
really need to close the window.

 694 passing (21s)
  12 pending

v4.0.6

Toggle v4.0.6's commit message
Version 4.0 requires io.js, see:

https://github.com/tmpvar/jsdom/blob/master/Changelog.md#400

ADDED preliminary support for the Fetch API (https://fetch.spec.whatwg.org/)

ADDED you can use the `browser.fetch` to retrieve any resources, using the
cookies, pipeline and all other browser settings

CHANGED upgraded to JSDOM 4.1

CHANGED use `browser.status` instead of `browser.statusCode` (HTML APIs use
`status` and `statusText`)

CHANGED `browser.resources` is now just an array of all resources requested when
processing the currently open window.  Resources no longer shared by all
windows, and other features (pipeline configuration, fetch resources) moved
elsewhere.

CHANGED separated pipeline from resources.  Use `browser.pipeline.addHandler` to
add request/response handler to the browser instance, or `Pipeline.addHandler`
to add handler to all new instances.

CHANGED pipeline API changed as well.  Request handler called with browser
instance and Fetch `Request` object, can return null or a Fetch `Response`
object.  Response handler called with browser instance, request and response
object, should return same or new response object.  Handlers no longer using
callbacks, if you need asynchronous behavior, return a promise.

FIXED empty `cookie` and `referer` header no longer sent assaf#881

FIXED added `navigator.appVersion` assaf#885

REMOVED `document.window`, use `document.defaultView` instead

REMOVED `browser.close` confusing method name, use `browser.window.close` if you
really need to close the window.

 694 passing (21s)
  12 pending

v4.0.5

Toggle v4.0.5's commit message
Version 4.0 requires io.js, see:

https://github.com/tmpvar/jsdom/blob/master/Changelog.md#400

ADDED preliminary support for the Fetch API (https://fetch.spec.whatwg.org/)

ADDED you can use the `browser.fetch` to retrieve any resources, using the
cookies, pipeline and all other browser settings

CHANGED upgraded to JSDOM 4.1

CHANGED use `browser.status` instead of `browser.statusCode` (HTML APIs use
`status` and `statusText`)

CHANGED `browser.resources` is now just an array of all resources requested when
processing the currently open window.  Resources no longer shared by all
windows, and other features (pipeline configuration, fetch resources) moved
elsewhere.

CHANGED separated pipeline from resources.  Use `browser.pipeline.addHandler` to
add request/response handler to the browser instance, or `Pipeline.addHandler`
to add handler to all new instances.

CHANGED pipeline API changed as well.  Request handler called with browser
instance and Fetch `Request` object, can return null or a Fetch `Response`
object.  Response handler called with browser instance, request and response
object, should return same or new response object.  Handlers no longer using
callbacks, if you need asynchronous behavior, return a promise.

FIXED empty `cookie` and `referer` header no longer sent assaf#881

FIXED added `navigator.appVersion` assaf#885

REMOVED `document.window`, use `document.defaultView` instead

REMOVED `browser.close` confusing method name, use `browser.window.close` if you
really need to close the window.

 694 passing (23s)
  12 pending

v4.0.4

Toggle v4.0.4's commit message
Version 4.0 requires io.js, see:

https://github.com/tmpvar/jsdom/blob/master/Changelog.md#400

ADDED preliminary support for the Fetch API (https://fetch.spec.whatwg.org/)

ADDED you can use the `browser.fetch` to retrieve any resources, using the
cookies, pipeline and all other browser settings

CHANGED upgraded to JSDOM 4.1

CHANGED use `browser.status` instead of `browser.statusCode` (HTML APIs use
`status` and `statusText`)

CHANGED `browser.resources` is now just an array of all resources requested when
processing the currently open window.  Resources no longer shared by all
windows, and other features (pipeline configuration, fetch resources) moved
elsewhere.

CHANGED separated pipeline from resources.  Use `browser.pipeline.addHandler` to
add request/response handler to the browser instance, or `Pipeline.addHandler`
to add handler to all new instances.

CHANGED pipeline API changed as well.  Request handler called with browser
instance and Fetch `Request` object, can return null or a Fetch `Response`
object.  Response handler called with browser instance, request and response
object, should return same or new response object.  Handlers no longer using
callbacks, if you need asynchronous behavior, return a promise.

FIXED empty `cookie` and `referer` header no longer sent assaf#881

FIXED added `navigator.appVersion` assaf#885

REMOVED `document.window`, use `document.defaultView` instead

 694 passing (23s)
  12 pending

v4.0.3

Toggle v4.0.3's commit message
Version 4.0 requires io.js, see:

https://github.com/tmpvar/jsdom/blob/master/Changelog.md#400

ADDED preliminary support for the Fetch API (https://fetch.spec.whatwg.org/)

CHANGED upgraded to JSDOM 4.1

CHANGED the resources implementation to use the Fetch API.  Pay attention to the
following breaking changes:

* To retrieve a resource, call `browser.resources.fetch`; the `request/get/post`
  methods are gone
* When checking on resources, the request and response objects are based on
  `Request`, `Response` and `Headers` as defined by the Fetch API
* In particular, Fetch (as well as XHR) has a `status` flag, whereas Node API
  has a `statusCode` in its HTTP API; Zombie is transitioning to use `status`
  everywhere to better mimic browser
* The pipeline implementation has changed as well: handlers are now called with
  reference to browser, use Fetch `Request` and `Response` objects, and can
  return an object or a promise, but no longer use callbacks

This actually makes the code simpler and easier to read, no seriously, try some
`async/await` for yourself. For example:

https://github.com/assaf/zombie/blob/fetch-api/src/resources.js#L123-L137

FIXED empty `cookie` and `referer` header no longer sent assaf#881

FIXED added `navigator.appVersion` assaf#885

REMOVED `document.window`, use `document.defaultView` instead

 694 passing (23s)
  12 pending

v4.0.2

Toggle v4.0.2's commit message
Version 4.0 requires io.js, see:

https://github.com/tmpvar/jsdom/blob/master/Changelog.md#400

ADDED preliminary support for the Fetch API (https://fetch.spec.whatwg.org/)

CHANGED upgraded to JSDOM 4.1

CHANGED the resources implementation to use the Fetch API.  Pay attention to the
following breaking changes:

* To retrieve a resource, call `browser.resources.fetch`; the `request/get/post`
  methods are gone
* When checking on resources, the request and response objects are based on
  `Request`, `Response` and `Headers` as defined by the Fetch API
* In particular, Fetch (as well as XHR) has a `status` flag, whereas Node API
  has a `statusCode` in its HTTP API; Zombie is transitioning to use `status`
  everywhere to better mimic browser
* The pipeline implementation has changed as well: handlers are now called with
  reference to browser, use Fetch `Request` and `Response` objects, and can
  return an object or a promise, but no longer use callbacks

This actually makes the code simpler and easier to read, no seriously, try some
`async/await` for yourself. For example:

https://github.com/assaf/zombie/blob/fetch-api/src/resources.js#L123-L137

FIXED empty `cookie` and `referer` header no longer sent assaf#881

FIXED added `navigator.appVersion` assaf#885

REMOVED `document.window`, use `document.defaultView` instead

 694 passing (23s)
  12 pending

v4.0.1

Toggle v4.0.1's commit message
Version 4.0 requires io.js, see:

https://github.com/tmpvar/jsdom/blob/master/Changelog.md#400

ADDED preliminary support for the Fetch API (https://fetch.spec.whatwg.org/)

CHANGED upgraded to JSDOM 4.1

CHANGED the resources implementation to use the Fetch API.  Pay attention to the
following breaking changes:

* To retrieve a resource, call `browser.resources.fetch`; the `request/get/post`
  methods are gone
* When checking on resources, the request and response objects are based on
  `Request`, `Response` and `Headers` as defined by the Fetch API
* In particular, Fetch (as well as XHR) has a `status` flag, whereas Node API
  has a `statusCode` in its HTTP API; Zombie is transitioning to use `status`
  everywhere to better mimic browser
* The pipeline implementation has changed as well: handlers are now called with
  reference to browser, use Fetch `Request` and `Response` objects, and can
  return an object or a promise, but no longer use callbacks

This actually makes the code simpler and easier to read, no seriously, try some
`async/await` for yourself. For example:

https://github.com/assaf/zombie/blob/fetch-api/src/resources.js#L123-L137

FIXES empty `cookie` and `referer` header no longer sent assaf#881

REMOVED `document.window`, use `document.defaultView` instead

 694 passing (23s)
  12 pending