-
errors when trying to test because not installed
-
### Bug:
When React renders a component with invalid props, it logs a warning.
If the same named component is rendered again, with the same invalid props, there is no warning.
### Demonstration:
htt…
-
Hey @EragonJ,
I used `nvm` to downgrade to `node@v5.1.1`, and this is the output of `npm i` is it normal from there?
I do not have any problem with the application itself after compilation, test a…
-
Since v1.7.5 I've been getting module not found errors and I believe it's related to `NODE_PATH` and likely related to this change with using `node-resolve`:
https://github.com/thlorenz/proxyquire/com…
-
1.7.4 everything worked.
broken test suite as a result from the update: (1.7.5 and 1.7.6 same issue)
```
SyntaxError: Unexpected token import
at exports.runInThisContext (vm.js:53:16)
at Modu…
-
Currently, we assert that log methods behave correctly in `test/local/log_tests.js`. But there is nowhere that we assert they are called correctly.
I can think of two ways to go about it:
1. As sugge…
-
Hi,
Please forgive me if I've missed something, but I would like to use proxyquire to mock multiple modules, let me give an example.
```
// JS File:
var one = require('one');
var two = require('t…
-
So I wanted to give this generator a shot (I already have some of my app built but I really like the sub-generators).
In any case, everything is working splendidly except one thing: unit testing.
I am…
-
# why does this matter?
npm installs are dominate by:
- download times
- local IO moving/copying etc files around
By reducing this overhead, we help reduce both on-disk bytes, number on files,…
-
If I have a module, the standard scenario with hot-reloading is that I want to alter the dependency and then have that new reference automatically pushed out to all modules that may have been loading …