rwhogg / gulp-jsduck Goto Github PK

View Code? Open in Web Editor NEW

1.0 1.0 2.0 939 KB

gulp plugin for jsduck

Home Page: https://rwhogg.github.io/gulp-jsduck/#!/api/GulpJSDuck

License: BSD 3-Clause "New" or "Revised" License

JavaScript 100.00%

gulp-jsduck's People

Contributors

Stargazers

Watchers

Forkers

gregjacobs olafleur

gulp-jsduck's Issues

Doesn't give error notifications if jsduck fails

Easiest way to demonstrate is by using the class keyword, since JSDuck doesn't support it.

Use Travis

We need to use Travis to make sure this doesn't break.

README should put "new gjsduck" in the right place

Suppress those ugly deprecation warnings.

Thread.exclusive is deprecated and whatnot

Modules Affected by "the liberation"

DO NOT USE THIS REPO UNTIL THIS ISSUE IS RESOLVED

node_modules//es5-ext/array/#/concat
node_modules//es5-ext/test/array/#/concat
node_modules//es5-ext/array/#/map
node_modules//es5-ext/test/array/#/map

Download script needs better logging

It should print a success message, and all failure cases should print a failure message

Will not be maintaining this as much in the future

a) I'm going to be going back to school soon and won't be able to spend as much time on this
b) My company's not going to be using it any more, so it's not likely that any employees are going to put a lot of work into it either.

I'm still maintaining this, but I'm not going to actively develop it.

You may want to try JSDoc instead of JSDuck.

Publish API documentation

A Github pages branch might be a good place to put it.

Release new version once jsduck has better logging

There's a package.json~ included in the download

Doesn't work when files are in subdirectories

You can tell from the error message currently seen in rwhogg/same-as-upstream