Shouldn't dispose of iframe after run
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- api
Research direction
Start by locating where this module creates and disposes its iframe or real context after each run. Compare that lifecycle with the Node vm example in the issue, then verify that a value assigned to Array in one run remains available in a later run using the same context.
Written by the indexing model from the issue text.
Description
In node vm:
var c = vm.createContext({});
vm.runInContext('Array.foo = 1', c);
assert(1 === vm.runInContext('Array.foo'));
And that's not the case in this module because it disposes of iframe (real context) after each run.
- Dominant language
- JavaScript
- Stars
- 205
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from browserify/vm-browserify
-
Difficulty 1/5 Under an hour Newbie friendliness 20/100
browserify/vm-browserify#31 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
browserify/vm-browserify#30 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
browserify/vm-browserify#25 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
browserify/vm-browserify#24 · 10 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
browserify/vm-browserify#23 · 3 comments ·
All issues in browserify/vm-browserify
Similar issues
-
external-issue to-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
LearningCircuit/local-deep-research#7067 ·
Maintainers usually reply within 1 day
-
automated issue report
Difficulty 1/5 Under an hour Newbie friendliness 65/100
lirantal/discoprint#32 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day