Running frisby seems to require frisby module installed locally.

[davezen1]

I received module not found errors when attempting to run frisby from the command like so:

jasmine-node spec/api/

I installed frisby globally like so:

npm install -g frisby

My node version is : v0.10.4 global only and frisby version 0.6.7 locally and globally

[kvarkson]

If your npm version 1.0+ take a look at http://blog.nodejs.org/2011/04/06/npm-1-0-link/#link_global_local link. Just link your global module to the local repository and this is it.

It works for me.

[vlucas]

Did you get this resolved with @kvarkson's comment?

[sacashgit]

I am getting the exact same error.. Not able to use frisby for API testing..

[shahdhruvin]

I tried what @kvarkson suggested above, like this:
Using the admin user (sudo su)
frisby$npm link frisby
/usr/local/lib/node_modules/frisby/node_modules/frisby -> /usr/local/lib/node_modules/frisby

I still get the exact same error:
jasmine-node spec/api/
Exception loading: /Users/dvin2684/try_frisby/spec/api/first_spec.js
{ [Error: Cannot find module 'frisby'] code: 'MODULE_NOT_FOUND' }

Please help !

[shahdhruvin]

Try using absolute PATH to frisby:
Like this: var frisby = require('/usr/local/lib/node_modules/frisby');
Instead of: var frisby = require('frisby');

It worked for me.

[vlucas]

The best solution is to require frisby in your package.json file so you can require it with just require('frisby') instead of installing it globally.

[harirordeveloper]

i followed shahdhruvin comment
Thanks guys worked for me :)

[benoror]

isn't it expected to work globally out of the box, the same way jasmine-node does?

[yuankui]

I follow @vlucas advice, add a package.json file

{
    "name": "mytest",
    "version": "1.0",
    "dependencies": {
        "frisby": "*"
    }
}

and run npm install or npm link
then i finnaly can require("frisby") directly in my test script

[RobertHerhold]

Why not just do npm install frisby --save-dev and then require it later var frisby = require('frisby') ?

Pretty much what @yuankui said, but shorter and appropriately defined as a development dependency. :)

[yuankui]

@RobertHerhold that's cool

and I just find another way, export NODE_PATH="'$(npm root -g)'"

choose your like

[marcin-wosinek]

I'm sure frisby should be managed as a dev-dep. Api changes are likely, and users will be better of updating their test suites gradually.

I've PR change in documentation:
vlucas/frisby-site#4