deepak1556 / gulp-browserify

Bundle modules with BrowserifyJS
MIT License
195 stars 45 forks source link

Add deprecation warning to npm #78

Closed k88hudson closed 7 years ago

k88hudson commented 9 years ago

Would you consider adding a deprecation warning to npm?

https://www.npmjs.org/doc/cli/npm-deprecate.html

dutzi commented 9 years ago

+1

deepak1556 commented 9 years ago

yup added, thanks

Pomax commented 9 years ago

https://www.npmjs.com/package/gulp-browserify doesn't show any deprecation, can you update the README.md so that there's a "this package is deprecated! Please use plain browserify instead" or something directly below the main heading? =(

deepak1556 commented 9 years ago
$ npm install gulp-browserify
npm WARN deprecated gulp-browserify@0.5.0: package is no longer maintained
gulp-browserify@0.5.0 node_modules\gulp-browserify
├── browserify-shim@2.0.10 (through@2.3.6)
├── readable-stream@1.1.13 (isarray@0.0.1, inherits@2.0.1, string_decoder@0.10.3
1, core-util-is@1.0.1)
├── through2@0.4.2 (readable-stream@1.0.33, xtend@2.1.2)
├── gulp-util@2.2.20 (minimist@0.2.0, lodash._reinterpolate@2.4.1, vinyl@0.2.3,
through2@0.5.1, multipipe@0.1.2, chalk@0.5.1, lodash.template@2.4.1, dateformat@
1.0.11)
└── browserify@3.46.1 (duplexer@0.1.1, xtend@3.0.0, inherits@2.0.1, punycode@1.2
.4, string_decoder@0.0.1, console-browserify@1.0.3, url@0.10.2, constants-browse
rify@0.0.1, tty-browserify@0.0.0, defined@0.0.0, util@0.10.3, builtins@0.0.7, pa
th-browserify@0.0.0, domain-browser@1.1.3, subarg@0.0.1, stream-browserify@0.1.3
, shallow-copy@0.0.1, https-browserify@0.0.0, timers-browserify@1.0.3, process@0
.7.0, querystring-es3@0.2.0, os-browserify@0.1.2, browser-resolve@1.2.4, crypto-
browserify@1.0.9, concat-stream@1.4.7, buffer@2.1.13, assert@1.1.2, events@1.0.2
, stream-combiner@0.0.4, commondir@0.0.1, shell-quote@0.0.1, vm-browserify@0.0.4
, resolve@0.6.3, syntax-error@1.1.2, browserify-zlib@0.1.4, JSONStream@0.7.4, de
ep-equal@0.1.2, derequire@0.8.0, http-browserify@1.3.2, deps-sort@0.1.2, glob@3.
2.11, parents@0.0.3, insert-module-globals@6.0.0, module-deps@2.0.6, browser-pac
k@2.0.1, umd@2.0.0)

isnt tat the deprecation warning required or am i missing something ? anyways will add in the readme, thanks :)

Pomax commented 9 years ago

it definitely is, but that only shows up when you use npm, the command. When people are browsing npmjs.org for a suitable browserify package for gulp (not realising browserify is that package =) they won't see that gulp-browserify is deprecated in favour of just using browserify itself. But with the new readme they will! yay!