hildjj / hildjj/node-inspect-extracted
Objects with null prototypes lose type information
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 19
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Code like this:
class Foo {}
const a = new Foo();
Object.setPrototypeOf(a, null);
inspect(a);
expected: [Foo: null prototype] {}
actual: [Object: null prototype] {}
Contributor guide
No contributing guide indexed for this repository
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 running the provided JavaScript reproduction and tracing the inspect(a) entry point. Compare how the class name and null prototype are identified for Foo versus Object. Done means the example produces [Foo: null prototype] {} instead of [Object: null prototype] {}.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100