callBound: support `--frozen-intrinsics`/lockdown?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
When `node` is invoked with `--frozen-intrinsics`, many data properties become getters. `RegExp.prototype.exec` is one example.
Should callBound automatically detect this at all? If so, should it detect `--frozen-intrinsics` specifically, or not? Either way, would it have to hardcode a list of the exact same data properties that frozen-intrinsics (and SES) convert to getters? (or alternatively, hardcode a list of all the builtins that are supposed to be getters, and auto-handle the rest).
See https://github.com/inspect-js/is-regex/issues/34.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing callBound with Node's --frozen-intrinsics and RegExp.prototype.exec, then read inspect-js/is-regex#34 for related behavior. Done means deciding and documenting whether frozen-intrinsics getters should be detected or handled, with the behavior verified under that flag.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100