mhevery / jasmine-node Goto Github PK
View Code? Open in Web Editor NEWIntegration of Jasmine Spec framework with Node.js
License: MIT License
Integration of Jasmine Spec framework with Node.js
License: MIT License
I installed the package through npm, but kept getting Error: Cannot find module
when running coffeescript specs. I managed to fix the issue by adding the --coffee
argument which was missing from the cli.js
file's switch statement.
The code is correct in the master branch so I haven't attached a pull request. Could this be related to the invalid package.json? See ticket #29.
Hello,
I've another thing how we could improve jasmine-node, but first want to discuss it with you. How about to add to CLI tag --include PATH, which will first for you add the PATH to the node libraries?
Then you can more easily reference components, you are testing in the jasmine suite. The idea comes from expresso, also quite popular way how to test node.js apps. Let me know what do you think. Its kind of easy to add.
I'm doing a decently significant refactor job relating to #51 (indirectly #46), and I want to make sure not to break any existing functionality. I see that there's already a spec
folder in the project, but attempting to run it with jasmine-node (./bin/jasmine-node ./spec
) produces an error.
Can I (and other developers) have some guidance in the README on how to properly run the tests for the project?
FWIW the error generated in my fork is:
>./bin/jasmine-node ./spec
node.js:134
throw e; // process.nextTick error, or 'error' event on first tick
^
Error: Cannot find module 'test'
at Function._resolveFilename (module.js:317:11)
at Function._load (module.js:262:25)
at require (module.js:346:19)
at Object.<anonymous> (/Users/eboto/jasmine-node/jasmine-node/spec/include/include_spec.js:1:74)
at Module._compile (module.js:402:26)
at Object..js (module.js:408:10)
at Module.load (module.js:334:31)
at Function._load (module.js:293:12)
at require (module.js:346:19)
at Object.executeSpecsInFolder (/Users/eboto/jasmine-node/jasmine-node/lib/jasmine-node/index.js:149:5)
I'm trying to get up and running with jasmine-node (I am not using npm), and can't quire figure out the intended use of various files. If I end up using it, I plan to package it as a zero install (www.0install.net) feed. The requirements for this are pretty simple, and mostly about relocation:
Right now it looks like putting pwd/
lib into $NODE_PATH will satisfy the first requirement. For the second one, it seems like it should either be cli.js or specs.js. cli.js didn't work for me, but isn't mentioned in the readme so maybe it's not meant as a front-end for running jasmine. I also tried running specs.js, but it does not do well at being run from anything but the current location, because:
This actually seems backwards to what I would expect - I would have thought you'd want to add __dirname + '/lib' to require.paths (although this should be unnecessary if you set $NODE_PATH appropriately), and that you'd run specs from "./spec", rather than the spec directory from wherever jasmine is installed.
To clarify what I'd like, imagine I have jasmine-node checked out into /some/random/path/jasmine-node. I would like to be able to run something like the following, from ~/dev/my-project (which has a spec directory):
~/dev/my-project $ export $NODE_PATH=/some/random/path/jasmine-node/lib
~/dev/my-project $ node /some/random/path/specs.js
Is this or something like it possible?
Can we rename the shell command to simply 'jasmine'? Possible? jasmine-node is pretty ugly. Is there some kind of conflict with another tool?
If there is a conflict, jasmine-test would be preferable to jasmine-node, since the 'node' part is pretty redundant. Imagine if every node commandline tool had -node at the end. yuck.
The installation documentation should be a little bit more detailed. Even with installation via npm people have issues configuring their NODE_PATH and seem confused at how the cli should be run.
Perhaps add some notes about how to setup a basic project including a sample Spec, a sample javascript file under test, including all the necessary requires, as well as how this would be run from the command line.
Using version 1.0.9 installed via npm, I have found that if I iterate over a list of values to test (for example, invalid email or url characters), this test fails if it is the first or only test in the spec file. If it is second, then it works. Am I doing something wrong or is this a bug? I created gist 1212065 ( https://gist.github.com/1212065 ) which shows both the broken version and the working version that uses a fake test to "prime" jasmine.
I just tried to install the latest npm install jasmine-node -g
and I got -bash: /Users/Craig/local/node/bin/jasmine-node: No such file or directory
when trying to run jasmine-node
at the command line.
Also using jasmine = require('jasmine-node')
in a Cakefile threw No such file or directory '/Users/Craig/inertia/test'
I'm currently on my windows machine with node version 0.6.7 and npm 1.1.0-beta-10. I installed jasmine-node with:
npm install jasmine-node -g
when i run command
jasmine-node spec
the output looks like:
Finished in 0 seconds
0 tests, 0 assertions, 0 failures
When uninstalled and installed version 1.0.17 (which i used few days ago on linux) i got:
..........
Finished in 0.012 seconds
10 tests, 16 assertions, 0 failures
I have three specs in spec folder, named *.spec.js
Are there any changes so my old spec files are not recognized?
This isn't so much an issue as a question - have you tried to debug into tests with node-inspector or something similar?
Seems logical to me to write asyncSpecWait() at the end of the spec - meaning I finished everything and now I am waiting for async function. But I may not know whether function is async or not and still want to keep the same spec.
I added simple spec to demonstrate my requirements:
describe('async spec', function () {
it('finishes when wait is called before done', function () {
jasmine.asyncSpecWait();
jasmine.asyncSpecDone();
});
it('should finish when done is called before wait', function () {
jasmine.asyncSpecDone();
jasmine.asyncSpecWait(); //will timeout
});
});
What do you think? Should this order matter?
When trying to run jasmine-node
with node 0.5.x it throws a fit.
throw e; // process.nextTick error, or 'error' event on first tick
^
Error: require.paths is removed. Use node_modules folders,
or the NODE_PATH environment variable instead.```
To try to keep my tests manageable, I wanted to split them across files. I tried naming those files things like 000_... 001_... to try to get them to execute in a specific order, but looking at the code, it seems like the filenames of the specs become irrelevant once they've been loaded.
Is there any way to control the ordering of suite execution that I'm not aware of? If not, this would be a nice feature to have.
Currently the naming is not done following a "sane" standard, introducing new feature in "patch" releases.
Noticed I don't get any output for skipped suites/specs (using xdescribe/xit). Then I noticed this: https://github.com/mhevery/jasmine-node/blob/master/lib/jasmine-node/reporter.js#L112
Not sure if the issue is with jasmine-node or jasmine itself, so feel free to close this in anger if I've reported it to the wrong place ;).
I'm new to Jasmine and BDD, but I just wanted to leave a note to say that it was unclear to me that I needed the word "spec" in the .coffee or .js filename. I figured since the specs where in the spec folder that would be enough. Took me a while to figure it out too. Thanks.
jasmine-node seems really keen on truncating any output going to the console, it seems there's a hard limit on how much it can print or perhaps there's some kind of async issue that means that it doesn't have time to finish printing output.
Can something be done about this, it becomes frustrating when not able print the information needed to debug specs.
It also does this for the stack traces printed when any test fails, perhaps this is so it doesn't print out a massive stack trace for the entire running jasmine suite, but perhaps that means we need a different approach to executing the specs so can get sensible traces. I had a quick look around the code but couldn't see how to fix this myself, sorry. Any ideas?
Created this gist that shows it failing:
https://gist.github.com/1260389
You can see that it's calling the function and the output is being displayed, but toHaveBeenCalled() is failing to correctly detect it.
Jasmine-node fails for me when using node 0.6.0 with this error:
NODE_ENV=test node_modules/jasmine-node/bin/jasmine-node spec/controllers
The "sys" module is now called "util". It should have a similar interface.
... a few lines of output from my initialization code
Started
FATAL ERROR: v8::HandleScope::Close() Local scope has already been closed
I've installed jasmine-node with npm but there is no jasmine-node command available.
I've looked at the package.json. Seems that there is no "bin" file.
How do I use jasmine-node?
If your code runs past a timeout, the reporter logic in index.js
will explode. This is with the current version of jasmine-node in NPM, at least as of yesterday or so. I decided to file this bug on jasmine-node rather than jasmine itself, because the exception occurs in jasmine-node's reporter component.
Another aspect of the observed behaviour is puzzling, though. Notice that below that the test is printed as failing and then the exception occurs, but only once my timeout overbudget code completes (therefore, if my code waited forever, the test would never finish and fail, the timeout setting notwithstanding).
What actually is the intended behaviour? I would expect that jasmine would mark the test as failing and continue once the timeout was up (even if the code under test did continue to run and do things through the event queue).
F
/home/orospakr/code/mine/cardscience/node_modules/jasmine-node/lib/jasmine-node/index.js:52
text.split(/\n/).forEach(function(line){
^
TypeError: Cannot call method 'split' of undefined
at Object.removeJasmineFrames [as stackFilter] (/home/orospakr/code/mine/cardscience/node_modules/jasmine-node/lib/jasmine-node/index.js:52:8)
at /home/orospakr/code/mine/cardscience/node_modules/jasmine-node/lib/jasmine-node/reporter.js:81:50
at Array.forEach (native)
at /home/orospakr/code/mine/cardscience/node_modules/jasmine-node/lib/jasmine-node/reporter.js:79:21
at Array.forEach (native)
at Object.reportSuiteResults (/home/orospakr/code/mine/cardscience/node_modules/jasmine-node/lib/jasmine-node/reporter.js:74:24)
at [object Object].reportSuiteResults (/home/orospakr/code/mine/cardscience/node_modules/jasmine-node/lib/jasmine-node/jasmine-2.0.0.rc1.js:1508:39)
at [object Object].finish (/home/orospakr/code/mine/cardscience/node_modules/jasmine-node/lib/jasmine-node/jasmine-2.0.0.rc1.js:2169:21)
at [object Object].onComplete (/home/orospakr/code/mine/cardscience/node_modules/jasmine-node/lib/jasmine-node/jasmine-2.0.0.rc1.js:2216:10)
at [object Object].next_ (/home/orospakr/code/mine/cardscience/node_modules/jasmine-node/lib/jasmine-node/jasmine-2.0.0.rc1.js:1800:14)
Tried to change src_dir and spec_dir settings in spec/support/jasmine.json but that does not seem to work
It looks to me like the second argument to specs.load should be fileMatcher instead of matcher.
I really like jasmine-node as it adds some much-needed usability to my tests. Thank you for creating it!
When I began using it, I had sort of assumed that jasmine-node would run the tests in node.js itself. I discovered that this is not the case when I went to use require and some other stuff, finding that it caused errors. This fact was further reinforced by the failure of code which relies on certain ES5 features present in V8 but not in other JS implementations which caused the tests to pass in Chrome but fail in other browsers.
I am filing this to request that a change be made to allow tests to be run inside node.js itself instead of the browser. Can such a thing be done? Thanks!
After launched this command "jasmine-node --runWithRequireJs ."
Error: Cannot find module 'underscore' [...]
Done on global fresh install via npm.
It seems the underscore depedency is missing...
(nodejs v0.6.2, npm v1.1.0-beta-7)
Nice tool, thanks in advance!
I don't know if you do this, but I build my ValueObjects with an equals-method. So I can define my own conditions to the equality of two objects. These are to be compared by
obj1.equals(obj2)
As the standard matcher from jasmine doesn't check for this method, I wrote my own matcher:
toBeEqualTo: function(expected) {
return this.acutal.equals(expected);
}
TypeError: Cannot call method 'equals' of undefined
Really? I was quite sure about the rest of the code, so I reversed it:
toBeEqualTo: function(expected) {
return expected.equals(this.acutal);
}
Error: Expected { method : Function, equals : Function, ... } to be equal to { method : Function, equals : Function, ... } at ... bla
Huh? So now I'm confused. Are these objects undefined or equal but not equal?
Also, my objects have a toString/toJSON method, I like those to be used if I see them printed out.
Hi, when I run jasmine-node over tests and attempt to call the fail() method, I get this:
ReferenceError: fail is not defined
fail() is defined in Jasmine, though I'm not sure of jasmine-node is supporting that part of the API yet? I have yet to look at this in any depth though I intend to, and I'll follow up with additional info as I get it.
I use it like this, preferring the second case
describe('thing', function() {
it('should fail', function() {
fail();
});
it('should also fail', fail());
});
This is directly from jasmine-node suite.
$ jasmine-node spec; echo $?
....................................F
Failures:
1) should report failure (THIS IS EXPECTED)
Message:
Expected true to be falsy.
Stacktrace:
Error: Expected true to be falsy.
at new <anonymous> (/home/matteo/.nvm/v0.6.7/lib/node_modules/jasmine-node/lib/jasmine-node/jasmine-2.0.0.rc1.js:102:32)
at [object Object].toBeFalsy (/home/matteo/.nvm/v0.6.7/lib/node_modules/jasmine-node/lib/jasmine-node/jasmine-2.0.0.rc1.js:1171:29)
at [object Object].<anonymous> (/home/matteo/repository/jasmine-node/spec/nested/uber-nested/UberNestedSpec.js:8:20)
at [object Object].execute (/home/matteo/.nvm/v0.6.7/lib/node_modules/jasmine-node/lib/jasmine-node/jasmine-2.0.0.rc1.js:1001:15)
at [object Object].next_ (/home/matteo/.nvm/v0.6.7/lib/node_modules/jasmine-node/lib/jasmine-node/jasmine-2.0.0.rc1.js:1790:31)
at [object Object].start (/home/matteo/.nvm/v0.6.7/lib/node_modules/jasmine-node/lib/jasmine-node/jasmine-2.0.0.rc1.js:1743:8)
at [object Object].execute (/home/matteo/.nvm/v0.6.7/lib/node_modules/jasmine-node/lib/jasmine-node/jasmine-2.0.0.rc1.js:2070:14)
at [object Object].next_ (/home/matteo/.nvm/v0.6.7/lib/node_modules/jasmine-node/lib/jasmine-node/jasmine-2.0.0.rc1.js:1790:31)
at [object Object].start (/home/matteo/.nvm/v0.6.7/lib/node_modules/jasmine-node/lib/jasmine-node/jasmine-2.0.0.rc1.js:1743:8)
at [object Object].execute (/home/matteo/.nvm/v0.6.7/lib/node_modules/jasmine-node/lib/jasmine-node/jasmine-2.0.0.rc1.js:2215:14)
Finished in 1.124 seconds
37 tests, 68 assertions, 1 failure
0
As 1 spec failed, the status code should be 1, not 0.
I tried to pipe output to a file and didn't get the actual test output, I get just the following:
Started
�[32m.�[0m
I have a app on git hub that can be used to replicate problem:
You'll see that the test output doesn't contain the specification.
Running Node on Win7 with cygwin
Hey,
Would it not be better for the process.env.NODE_ENV
to run in test
mode. This then allows for configuring tests settings in an app like express specifically for the test runner
Currently, the jasmine backtraces on failed tests are more noise than signal; there has been a patch for that in jasmine master which according to jasmine/jasmine#5 should have been included in the jasmine 1.1.0 release.
However the maintainers seem to have jumped from 1.1.0rc4 to 2.0.0rc1, and in the meantime the missing signal in the backtraces is rather annoying.
Please consider updating the bundled jasmine, unless of course it breaks something :).
Is it possible to put specs in the tests folder instead?
Running the following spec
describe('root', function () {
describe('nested', function () {
it('nested statement', function () {
expect(1).toBeTruthy();
});
});
it('root statement', function () {
expect(1).toBeTruthy();
});
});
Produces the following output
Started
..
Spec root nested
it nested statement
Spec root
it undefined
it root statement
Finished in 0.002 seconds
2 tests, 2 assertions, 0 failures
Which means it's counting the correct number of specs (2) but it's producing 3 it statements. It seems like the second one "it undefined" is being generated due to the nested describe.
Can someone try to reproduce it?
Thanks
-w
The package.json file in NPM is:
{
"name" : "jasmine-node",
"version" : "1.0.1",
"description" : "DOM-less simple JavaScript BDD testing framework for Node",
"homepage" : [
"http://pivotal.github.com/jasmine" ,
"https://github.com/mhevery/jasmine-node"
],
"repository" : {
"type" : "git" ,
"url" : "https://github.com/mhevery/jasmine-node.git"
},
"keywords" : [
"testing",
"bdd"
],
"author" : "Misko Hevery <[email protected]>",
"contributors" : [
"Rajan Agaskar <[email protected]" ,
"Christian Williams <[email protected]" ,
"Davis W. Frank <[email protected]>",
,
"Matteo Collina <[email protected]>"
],
"maintainers" : "Martin Häger <[email protected]>",
"licenses" : [
"MIT"
],
"dependencies" : {
"coffee-script" : ">=1.0.0"
},
"bin" : "./bin/jasmine-node",
"main" : "./lib/jasmine-node"
}
There are two commas after Davis W. Frank's contributor entry, which makes the json file invalid.
Do you guys think it's also a good idea to run DOM related specs in jasmine-node? I am currently working on a fork to use jsdom and run specs in "its" context. In turn I can have a more coherent test environment not requiring the browser and also being able to use autotest/guard.
In some cases when spec fails I get this error and node process exits (using node v0.4.8).
Started
........F.
/usr/local/lib/node/.npm/jasmine-node/1.0.8/package/lib/jasmine-node/index.js:52
text.split(/\n/).forEach(function(line){
^
TypeError: Cannot call method 'split' of undefined
at Object.removeJasmineFrames [as stackFilter] (/usr/local/lib/node/.npm/jasmine-node/1.0.8/package/lib/jasmine-node/index.js:52:8)
at /usr/local/lib/node/.npm/jasmine-node/1.0.8/package/lib/jasmine-node/reporter.js:80:48
at Array.forEach (native)
at /usr/local/lib/node/.npm/jasmine-node/1.0.8/package/lib/jasmine-node/reporter.js:79:21
at Array.forEach (native)
at Object.reportSuiteResults (/usr/local/lib/node/.npm/jasmine-node/1.0.8/package/lib/jasmine-node/reporter.js:74:24)
at [object Object].finish (/usr/local/lib/node/.npm/jasmine-node/1.0.8/package/lib/jasmine-node/jasmine-1.0.1.js:2117:21)
at [object Object].onComplete (/usr/local/lib/node/.npm/jasmine-node/1.0.8/package/lib/jasmine-node/jasmine-1.0.1.js:2164:10)
at [object Object].next_ (/usr/local/lib/node/.npm/jasmine-node/1.0.8/package/lib/jasmine-node/jasmine-1.0.1.js:1749:14)
at [object Object].start (/usr/local/lib/node/.npm/jasmine-node/1.0.8/package/lib/jasmine-node/jasmine-1.0.1.js:1692:8)
This bug is introduced in v1.0.8. It makes hard to identify the error...
The same spec with v1.0.7 returns:
Started
........F.
answer
it calls answer method on the right channel
undefined
undefined
Error: TypeError: Object [object Object] has no method 'toBeTruthly'
at new <anonymous> (/usr/local/lib/node/.npm/jasmine-node/1.0.7/package/lib/jasmine-node/jasmine-1.0.1.js:94:50)
at [object Object].fail (/usr/local/lib/node/.npm/jasmine-node/1.0.7/package/lib/jasmine-node/jasmine-1.0.1.js:1963:27)
at [object Object].execute (/usr/local/lib/node/.npm/jasmine-node/1.0.7/package/lib/jasmine-node/jasmine-1.0.1.js:970:15)
at [object Object].next_ (/usr/local/lib/node/.npm/jasmine-node/1.0.7/package/lib/jasmine-node/jasmine-1.0.1.js:1739:31)
at [object Object].start (/usr/local/lib/node/.npm/jasmine-node/1.0.7/package/lib/jasmine-node/jasmine-1.0.1.js:1692:8)
at [object Object].execute (/usr/local/lib/node/.npm/jasmine-node/1.0.7/package/lib/jasmine-node/jasmine-1.0.1.js:2018:14)
at [object Object].next_ (/usr/local/lib/node/.npm/jasmine-node/1.0.7/package/lib/jasmine-node/jasmine-1.0.1.js:1739:31)
at [object Object].start (/usr/local/lib/node/.npm/jasmine-node/1.0.7/package/lib/jasmine-node/jasmine-1.0.1.js:1692:8)
at [object Object].execute (/usr/local/lib/node/.npm/jasmine-node/1.0.7/package/lib/jasmine-node/jasmine-1.0.1.js:2163:14)
at [object Object].next_ (/usr/local/lib/node/.npm/jasmine-node/1.0.7/package/lib/jasmine-node/jasmine-1.0.1.js:1739:31)
Finished in 0.006 seconds
5 tests, 17 assertions, 1 failure
I believe this is related to using waitsFor method, I have noticed it in async specs only...
Simple spec to reproduce:
describe('throwing spec', function () {
it('is bad', function () {
var completed = false;
var obj = { func: function() {
expect(completed).toBeFalsy();
completed = true;
}};
obj.func();
waitsFor(function () { return completed });
expect(function () { return false }).toBeThere(); //will throw
});
});
any reason why we can't change the command to just "jasmine" ?
command jasmine-node
is very verbose...
In the test folder I have a lot of spec files.
When adding a new one it would be nice if I could just run that one instead of all of the specs I have.
I just installed jasmine-node with npm and I noticed that bin wasn't linked to my bin folder. I did some research and it requires bin declaration in package.json. I tried that and it worked. So what is the reason, why this isn't declared by default? I'm quite new to node and npm, so I also want to learn this kind of details :)
Jasmine-node reports assertions failed/succeded, not number of tests, like the html report. Both could be more complete, but, in particular, node version could also report the number of tests.
When attempting to run on Teamcity, it fails due to the jasmine.TeamcityReporter not being present.
Apparently, the version of jasmine-reporters currently on npm is not the version that includes the correct reporter.
Proposed solutions:
1 - Get jasmine-reporters project to put their current version on npm, and update dependency for this project.
2 - Use git submodule to clone the current version of jasmine-reporters into node_modules
When manually updating the jasmine-reporters module, I could get it running no problems, but I would really like to be able to use the pure npm version of jasmine-node.
jasmine-node unfortunately doesn't come as a module (var jasmine = require('jasmine-node');) so the only option is to the use command line tool. And the command line tool blows up when when your specs are themselves AMD modules. I created a sample project to try to figure out how to test AMD modules with jasmine-node, if anyone wants to help out.
Thanks
I can name my specs xx_spec.js and xxSpec.coffee, but the helper files have to include an underscore. This is not consistent.
Also, I would like to just accumulate all my helpers in a helpers.js file, that is not possible either.
I'm currently using jasmine-node with zombiejs to run some async tests.
In some cases, I have nested async calls, for example :
it('displays the page correctly', function() {
zombie.visit(myUrl, function(err, browser, status) {
//a- Title on the page is correct
expect(browser.text('title')).toEqual('first page');
//b- There is an 'Add product' link
var addButton = browser.css('#addButton').length;
expect(addButton).toEqual(1);
//c- A click on the Add button links to the New Page
browser.clickLink('#addButton', function(err, browser, status) {
expect(browser.text('title')).toEqual('New Page')
jasmine.asyncSpecDone();
})
jasmine.asyncSpecWait()
})
})
In other cases, I have several async tests in the same suite :
describe('home page', function() {
it('loads the page correctly', function() {
zombie.visit(thisUrl, function(err, browser, status) {
expect(err).toBeNull();
expect(status).toBe(200);
jasmine.asyncSpecDone();
})
})
it('displays correctly', function(){
zombie.visit(thisUrl, function(err, browser, status){
//a- There is one form on the page
var theForm = browser.css("form");
expect(theForm.length).toBe(1);
expect(browser.css("#name").length).toBe(1);
jasmine.asyncSpecDone();
})
})
it('has the right interactions', function() {
zombie.visit(thisUrl, function(err, browser, status) {
//expect ...
jasmine.asyncSpecDone();
})
})
})
jasmine.asyncSpecWait()
Both snippets run fine, but I really need to better understand how to use asyncSpecDone() and asyncSpecWait(). A little documentation on it would be very nice (where to place each call, how many calls are needed, wha
Is there a way to programmatically run jasmine-node from within a node app?
I'm seeing some weirdness with jasmine-node 1.0.7 and node 0.4.11. My process never finishes. Who is supposed to send the 'exit' signal?
It would significantly help anyone who wants to run jasmine-node programmatically if the custom reporter implemented on index.js:65 were refactored into its own class: perhaps NodeReporter?
without said refactor, it's still possible to run the test runner, but difficult to get useful input!
Any way to add a 'watch' feature? where the tests auto restarts on file-spec / directory changes?
There's modules like nodemon
and supervisor
but I haven't figured out how to use it with jasmine-node yet...
Is there a generic unix command that execute a certain command on file/directory changes?
Thanks.
The only coffeeScript I saw was in the spec folder.
I just tried to run from HEAD, but I get this error:
TypeError: Object # has no method 'loadHelpersInFolder'
at Object. (/home/tim/gnome-shell/shellshape/jasmine-node/lib/jasmine/cli.js:30:9)
at Module._compile (module.js:404:26)
at Object..js (module.js:410:10)
at Module.load (module.js:336:31)
at Function._load (module.js:297:12)
at Array. (module.js:423:10)
at EventEmitter._tickCallback (node.js:126:26)
Is there a dependency I'm missing? (I'm not using npm or anything). The function doesn't seem to be defined anywhere in this repo:
$ ack -u loadHelpersInFolder
lib/jasmine/cli.js
30:jasmine.loadHelpersInFolder(SPEC_FOLDER, HELPER_MATCHER_REGEX);
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.