Skip to content
This repository has been archived by the owner on Nov 24, 2021. It is now read-only.

Make a workaround for the cssstyle package. #65

Closed
jansiegel opened this issue Jul 10, 2018 · 1 comment
Closed

Make a workaround for the cssstyle package. #65

jansiegel opened this issue Jul 10, 2018 · 1 comment

Comments

@jansiegel
Copy link
Member

Currently, one of the devDependencies is my fork of the cssstyle package. (More information here: jsdom/cssstyle#63).
This is not an optimal solution, plus it breaks npm audit, as it's not published to npm.

The new approach overwrites the Number prototype by adding toLowerCase and split methods for the tests, as they break on them specifically.

@jansiegel jansiegel self-assigned this Jul 10, 2018
jansiegel added a commit that referenced this issue Jul 10, 2018
- Force travis to use node 8
- Remove unneeded jest globals from the config
#65
jansiegel added a commit that referenced this issue Jul 10, 2018
* Add a workaround for the `cssstyle` package. #65

* - Extend the mocked methods
- Force travis to use node 8
- Remove unneeded jest globals from the config
#65
@wojciechczerniak
Copy link
Contributor

Fix for CSSStyleDeclaration in jsdom/cssstyle#52 was merged and released as 1.0.0: https://github.com/jsakas/CSSStyleDeclaration/releases/tag/v1.0.0

@jansiegel Maybe we should revert this workaround? 💔

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants