Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

whacko is no longer maintained. #392

Closed
deniak opened this issue May 31, 2016 · 4 comments · Fixed by #911
Closed

whacko is no longer maintained. #392

deniak opened this issue May 31, 2016 · 4 comments · Fixed by #911
Assignees
@deniak @jennyliang220
Labels
enhancement security

Comments

@deniak
Copy link
Member

deniak commented May 31, 2016

No description provided.

@tripu
Copy link
Member

tripu commented Jul 11, 2016

Shall we use cheerio instead?

@deniak
Copy link
Member Author

deniak commented Jul 11, 2016

I think so although it would be good if they add the support for parse5. It's a low priority anyway

@plehegar
Copy link
Member

jsdom is the way to go at the moment.

@deniak deniak self-assigned this Jun 19, 2018
@tripu tripu mentioned this issue Nov 26, 2018
Closed
@tripu tripu added the security label Nov 26, 2018
@tripu
Copy link
Member

tripu commented Nov 26, 2018

Moving this to the “current cycle” column; we're stuck with this npm vulnerability because of this dependency.

$ npm ls 'lodash@<4.17.5'
specberus@3.9.2
└─┬ whacko@0.19.1
  └── lodash@3.10.1

@jennyliang220 jennyliang220 mentioned this issue Jun 9, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@deniak deniak

@jennyliang220 jennyliang220

Labels
enhancement security
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Replace whacko with JSDOM, remove $ w3c/specberus
4 participants
@tripu @plehegar @deniak @jennyliang220