Solved: Testing package with local dependencies

I’m trying to run the tests of dalgard:jade with the local version of its dependency, dalgard:jade-compiler, but I can’t find anywhere to put a packages folder that will make the former package import the latter from anywhere but Atmosphere.

Any hints?


I can’t figure out what you exactly wanted to do.
Would you like to force a specific package version to be used ?
Or would like to use a package that is not on Atmosphere ?


dalgard:jade has a dependency, namely dalgard:jade-compiler. When running the tests of dalgard:jade, it imports dalgard:jade-compiler from Atmosphere.

Instead, I want to use a local copy of dalgard:jade-compiler.

Without this possibility, I can’t edit dalgard:jade-compiler and run the tests of dalgard:jade against the changes, without first pushing the edits to Atmosphere (not an option).

If your dalgard:jade-compiler package is in your packages folder then it will use.
Think to update the package version number to be sure you will use the one you currently edit from within your project.

If you want to reference a package from another project then check
It enables you to add a dependency to a private package from your github.

Hope this help.


Thanks, but I’m talking about when I test the package with meteor test-packages ./.

I suppose it might help if I do it in the context of a project, hmm… But it’s not very practical having to create a new project, when a package can be tested alone with .../mypackage$ meteor test-packages ./.


export PACKAGE_DIRS="/path/to/your/custom/packages/folder

and put the dalgard:jade-compiler package in the dir above

@sam: Sounds right, but won’t that prevent importing any package that aren’t in that directory?

I think it just means it will try there first, then it will try atmosphere for the rest

Ok, so your dalgard:jade-compiler is in project packages alongside with dalgard:jade right ?

If you change the version number in package.js of dalgard:jade-compiler and force to use this version number in dalgard:jade/package.js it should work.

api.onUse( [

That’s right.

Well, that method hasn’t worked before, though – but come to think about it, I may have forgotten the equals sign in front of the version number.

These solutions both work for testing the local version of a dependency:

  • Using PACKAGE_DIRS (for testing a package that isn’t inside a project)
  • Writing the meteor test-packages command inside a project

Thanks for your help!

1 Like