Releases: typhonjs-node-esdoc/esdoc-plugin-jspm
Releases · typhonjs-node-esdoc/esdoc-plugin-jspm
0.6.6
0.6.6 (2016-05-02)
- Updated dependencies / typhonjs-config-jspm-parse to v0.6.0
- Separated package parsing to
packageParser.js - Additional data is added to normalized package data including Github / NPM links.
- Any ESDoc tags that are associated with JSPM managed packages now include
tag.packageDataandtag.packageManager. - Export to global data:
global.$$esdoc_plugin_jspm =
{
childPackageMap, // All child packages parsed from System / config.js
jspmDevPackageMap, // Top level JSPM packages taken from options and / or package.json jspm.devDependencies.
jspmPackageMap, // Top level JSPM packages taken from options and / or package.json jspm.dependencies.
normPackageData, // Normalized package data for all JSPM managed packages.
normPackageDataESDoc, // Normalized package data for all ESDoc enabled JSPM managed packages.
rootDirName, // Root directory name.
rootPackageName, // Root package name.
rootPath, // Root path
topLevelPackages, // All top level dependencies and dev dependencies.
uniqueDeps, // Unique package dependencies
uniqueDevDeps, // Unique package dev dependencies
uniqueDepsAll // All unique package dependencies
};
An example of retrieving data follows:
const { normPackageData, normPackageDataESDoc, rootDirName, rootPackageName, rootPath } = global.$$esdoc_plugin_jspm;
0.6.5
0.6.4
0.6.3
0.6.0
0.5.0
0.4.1
0.4.0
0.3.0 - Going full auto!
- Feat
- Added automatic parsing of
package.jsonentries forjspm.dependencies. It is no longer necessary to specify anoption.packagesarray for JSPM packages to link inesdoc.json. Any valid JSPM package with anesdoc.jsonfile in the respective root path will linked including any valid child dependencies defined inconfig.js.
- Added automatic parsing of