Updates for gulp-footer

gulp-community / gulp-footer

Gulp extension to add a footer to file(s) in the pipeline

MIT License

9 stars 9 forks source link

Updates for gulp-footer #15

Closed tracker1 closed 4 years ago

tracker1 commented 4 years ago

Update dependencies for https://github.com/gulp-community/gulp-footer/issues/14
Swap mocha for jest, easier coverage output
Add github workflow for test and publish (remove travis.yml)
Add coverage to gitignore file
Fix warnings for deprecated Buffer constructor use.

@contra @phated - you'll need to add an npm_token secret on this project for publish, I've added you both on npm for this package. You will also need to add this project to coveralls.io (free for open-source projects) in order for the coverage badge to work.

Checkout/clone the latest master after merge then run one of the following:

npm run publish-major
npm run publish-minor
npm run publish-patch

phated commented 4 years ago

The plan is to require 2FA on gulp-community so automated releases won't work, unfortunately.

ZhangChengLin commented 4 years ago

The plan is to require 2FA on gulp-community so automated releases won't work, unfortunately.

@tracker1

zdfowler commented 3 years ago

Not seeing this actually in the npm package - @tracker1 is this something that can be picked up?

phated commented 3 years ago

@zdfowler what exactly are you looking for? I just got the update workflow working for gulp-pug and will be applying it to the other gulp-community packages when I have time.

zdfowler commented 3 years ago

Expecting to see the changes in package.json that were part of this PR to be in master.

For example, "lodash.template": "^4.5.0", is listed in showing in a8da84 but not seeing it in master, nor the package published to npm.

zdfowler commented 3 years ago

@tracker1 ^^ and it should also address #16

phated commented 3 years ago

That CVE doesn't matter unless you are somehow passing un-sanitized user input to your gulp tasks (and that would be actually insane).