facebookarchive/prepack

Model the browser DOM using JSDOM

Open

#475 opened on Apr 27, 2017

View on GitHub
 (2 comments) (8 reactions) (0 assignees)JavaScript (14,268 stars) (520 forks)batch import
design neededhelp wanted

Description

https://github.com/tmpvar/jsdom

This would need to mark all its objects as intrinsic automatically from inside the Prepack realm.

Constructors also need to be able to track how they were constructed. It can't construct using new HTMLDivElement() but it could do document.createElement("div").

I think this can mostly be achieved by treating everything as abstract and simple but it would be even nicer to be able to track expected side-effects so that even more can be done.

Contributor guide

Tech stack
javascript
Domain
toolingperformance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaScriptJSDOMPrepack internalscompiler optimization concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
Review Prepack's intrinsic object model in the source code (e.g., src/intrinsics directory). Study the JSDOM library's DOM class hierarchy and how objects like HTMLDivElement are created. The issue suggests marking all JSDOM objects as intrinsic and tracking constructor usage (e.g., document.createElement). Explore how Prepack can abstract these objects and track side effects to enable more aggressive optimizations. Note that the repository is archived, so further development may not be active.