Phantomas

Latest version: v0.2.3

Safety actively analyzes 619647 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 6

1.18.0

New version of Phantomas is out. Support for providing **more than just one cookie** has been added (see 667) and **latency information** (i.e. time for first byte metric) is now printed out as a part of offenders for static assets by type counter (see 668).

Please note that **support for Node.js 0.12.x has been dropped**. According to [Node's LTS schedule](https://github.com/nodejs/LTSlts-schedule) v0.12 release support will end 2016-12-31.

As always, the full list of changes can be found below.

_Enjoy new Phantomas and Merry Christmas :christmas_tree: !_

Bug fixes
- 672 - analyze-css `runScript` path invalid (Windows issue)

Enhancements
- 667 - Add support for multiple cookies
- 668 - Latency for all assets

Internals
- 605 - Update dependencies to get rid of vulnerabilities reported by snyk.io
- 673 - Run TravisCI tests using Node.js 7.x
- 676 - Bump slimerjs to 0.10.2 (submitted by DevSide)
- 678 - Drop support for Node.js 0.12.x

Architecture
- 670 - fix simple-queue by enforcing only one `done()` call per push (fix provided by nathanial, thanks!)

1.17.0

This release brings [phantomas on died](https://github.com/macbre/phantomas/issues?q=is%3Aopen+is%3Aissue+label%3A%22Phantomas+on+diet%22) - less dependencies mean quicker `npm install` (see 625 and 661).

From `analyze-css` side: `complexSelectorsByAttribute` and `universalSelectors` metrics were removed (662).

Enhancements
- 500 - Transfer proxy config to `analyze-css` (by gmetais)
- 625 - Move `elasticsearch` to an external npm module
- 661 - make PhantomJS and SlimerJS optionalDependencies
- 662 - Consider removing universal selectors rule

Bug fixes
- 655 - "JSON parse error" when analyze-css result is > 64K (by gmetais)
- 664 - Run fails when phantomas is an npm 3 dependency (by gmetais)

Internals
- 660 - Update dependencies

1.16.0

Enhancements
- 623 - Try to import reporter as external dependency (by EFF)

Bug fixes
- 622 - `XMLHttpRequest` not being counted in `ajaxRequests`
- 636 - Analyze-css failing without incrementing `cssParsingErrors` (by gmetais)
- 641 - Fix average metrics from analyze-css
- 643 - Fix cache detection: max-age should overtake expires (by gmetais)
- 644 - Update phone and tablet user-agents (by gmetais)

Internals
- 624 - Updated reject promise to return a single argument (by alex-e-leon)
- 626 - TAP: use a smaller dependency that only renders the TAP output
- 627 - Make analyze-css dependency a bit smaller
- 632 - What does EXIT_CONFIG_FAILED do?
- 646 - Travis: run under the latest Node.js v6.x
- 653 - Update dependencies

1.15.1

This minor release brings a bug fix for PhantomJS cookies handling regression:

621 - Quick fix for cookie regression in PhantomJS 2.1 (by gmetais)

1.15.0

From now on **phantomas uses PhantomJS 2.1.x only** (**the support for the legacy 1.9.x version has been removed** - 602). Please use `--webkit` or `--gecko` command line options to switch between engines. `--webkit2` no longer works.

The full list of changes (mostly bug fixes) can be found below.

Changelog

Improvements
- 594 - Added aws cloudwatch as reporter (by EFF)
- 578 - Add offenders to cssNotMinified, cssLength, cssRules, cssSelectors & cssDeclarations

Bug fixes
- 613 - Automatically allow main domain when using --allow-domain (by gmetais)
- 612 - Replace `.once` by `.on` for metrics consistency after a JS redirection (by gmetais)
- 607 - Fix init event re-triggered at the end of the page load (by gmetais)
- 596 - Json output is invalid and truncated for large reports
- 587 - Analyze-Css module incorrect processing of query parameters

Internals
- 616 - Travis: cache node modules
- 615 - async / elasticsearch: update dependencies
- 609 - Added additional information to promise reject function (by alex-e-leon)
- 608 - Remove the webkit2 solution (by gmetais)
- 603 - glob / http-server: update dependencies
- 602 - Use PhantomJS 2.x only

1.14.0

It's been a while since the last release of `phantomas`, but I believe it was worth waiting for ;)

Thanks to 488 and 592 **phantomas now uses PhantomJS 2.1.x official binaries**.
You can use `--engine=webkit` to switch to the legacy 1.9.x version (it will be removed in phantomas 1.15).

DNS and Connect timings (introduced in 477) were reverted (575) as they provided zero in 99,9% of cases in both SlimerJS and PhantomJS 2.

The full list of changes can be found below.

Changelog

Bug fixes
- 558 - Getting 255 (PhantomJS 2.0.0 crashes) for some sites
- 569 - Resolved promise with error code 1
- 575 - Revert "DNS and Connect timings"
- 581 - CSV responses inconsistent
- 586 - npm install should install without compile error under Node 4+ (by dimichgh)
- 583 - add extra err check for analyzeCss result (by ingoclaro)
- 589 - Fix --allow-domain option (by gmetais)

Internals
- 488 - Upgrade to PhantomJS 2.1.1
- 571 - Run tests using node v4.2.x on Travis
- 573 - Use PhantomJS 2.0.1-static
- 585 - Update SlimerJS min version (by gmetais)
- 592 - `webkit2`: make it a default engine

Page 1 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.