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

Reduce npm package bloat #878

Open
1 of 4 tasks
strager opened this issue Oct 24, 2022 · 2 comments
Open
1 of 4 tasks

Reduce npm package bloat #878

strager opened this issue Oct 24, 2022 · 2 comments
Labels
performance Slowness or potential optimization

Comments

@strager
Copy link
Collaborator

strager commented Oct 24, 2022 •
edited

@strager
Copy link
Collaborator Author

strager commented Oct 24, 2022

We only use jsdom for testing the web demo marking code. We could just drop testing for that code, or we could switch to another implementation (e.g. refs/archive/web-demo-absolute-marking, which jsdom can't test anyway).

@strager strager added the performance Slowness or potential optimization label Oct 24, 2022
@strager
Copy link
Collaborator Author

strager commented Oct 26, 2022

jsdom dropped in 830df6b (after removing its need in commit e7c6c79).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
performance Slowness or potential optimization
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@strager