moog-require - npm Package Compare versions

Comparing version 0.0.3 to 0.1.0

package.json

		{
		"name": "moog-require",
		"version": "0.0.3",
		"version": "0.1.0",
		"description": "moog-require extends moog with support for type definitions in local files and npm modules.",
		@@ -10,3 +10,3 @@ "main": "index.js",
		"resolve": "^1.0.0",
		"moog": "~0.0.1"
		"moog": "~0.1.0"
		},
		@@ -13,0 +13,0 @@ "devDependencies": {

README.md

		@@ -247,1 +247,6 @@ [![Build Status](https://travis-ci.org/punkave/moog-require.svg?branch=master)](https://travis-ci.org/punkave/moog-require)
		However, you may explicitly `create` a type that exists only in the project level folder and/or npm.

		## Changelog

		0.1.0: compatible with `moog` 0.1.0 in which the `__meta` property became an object with `chain` and `name` properties.

test/test.js

		@@ -704,10 +704,11 @@ var assert = require('assert');
		assert(module.__meta);
		assert(module.__meta[0]);
		assert(module.__meta[0].dirname === __dirname + '/node_modules/metadataNpm');
		assert(module.__meta[1]);
		assert(module.__meta[1].dirname === __dirname + '/project_modules/metadataNpm');
		assert(module.__meta[2]);
		assert(module.__meta[2].dirname === __dirname + '/project_modules/metadataProject');
		assert(module.__meta[3]);
		assert(module.__meta[3].dirname === __dirname + '/project_modules/metadataExplicit');
		assert(module.__meta.chain);
		assert(module.__meta.chain[0]);
		assert(module.__meta.chain[0].dirname === __dirname + '/node_modules/metadataNpm');
		assert(module.__meta.chain[1]);
		assert(module.__meta.chain[1].dirname === __dirname + '/project_modules/metadataNpm');
		assert(module.__meta.chain[2]);
		assert(module.__meta.chain[2].dirname === __dirname + '/project_modules/metadataProject');
		assert(module.__meta.chain[3]);
		assert(module.__meta.chain[3].dirname === __dirname + '/project_modules/metadataExplicit');
		return done();
		@@ -714,0 +715,0 @@ });

New alerts