https://github.com/bitwit/proxyquireify-phantom-menace
proof of issue with prozyquireify and phantomJS
https://github.com/bitwit/proxyquireify-phantom-menace
Last synced: about 1 year ago
JSON representation
proof of issue with prozyquireify and phantomJS
- Host: GitHub
- URL: https://github.com/bitwit/proxyquireify-phantom-menace
- Owner: bitwit
- Created: 2015-06-18T20:49:02.000Z (almost 11 years ago)
- Default Branch: master
- Last Pushed: 2015-07-03T21:06:28.000Z (almost 11 years ago)
- Last Synced: 2025-03-24T03:37:42.584Z (about 1 year ago)
- Language: JavaScript
- Size: 141 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: Readme.md
Awesome Lists containing this project
README
# The Proxyquireify PhantomJS Menace
This repo is intended to prove an existing problem with PhantomJS that affects proxyquirify (and possibly other libraries that use 'callee'). Original discussion here: https://github.com/thlorenz/proxyquireify/issues/35
It can now be fixed with this module: https://github.com/bendrucker/phantom-ownpropertynames
This repo remains here for posterity, in case anyone else stumbles on this problem
1. run `node browersrifySpec.js`
2. run `grunt karma`
3. should suceed in Chrome but fail in PhantomJS