luftywiranda13 / remove-lockfiles Goto Github PK

View Code? Open in Web Editor NEW

4.0 2.0 0.0 349 KB

Prevent committing lockfiles

License: MIT License

JavaScript 100.00%

git git-hooks hooks pre-commit npm yarn commit cli cli-app lockfile

remove-lockfiles's Introduction

remove-lockfiles

Prevent committing lockfiles

Why

Lockfiles are for apps, not for libraries/packages
Listing lockfiles in .gitignore is considered a bad approach
Unstaging only will introduce new problems
Uses force-del to get rid of lockfiles
No need to force contributors to use npm or yarn
No need to use 2 extra dot files (.npmrc and .yarnrc) to avoid generating lockfiles
Works on macOS, Linux, and Windows

Installation

npm install --save-dev remove-lockfiles

Usage

Pre-commit hook

Install husky:

npm install husky --save-dev

Edit package.json to include this configuration:

{
  "scripts": {
    "precommit": "remove-lockfiles"
  }
}

Looking for alternative to husky? We can also use remove-lockfiles with pre-commit.

CLI

Install remove-lockfiles globally:

npm install --global remove-lockfiles

Run the script:

$ remove-lockfiles --help

  Usage
    $ remove-lockfiles [path|options]

  Options
    --shrinkwrap  Remove `npm-shrinkwrap.json` if found

  Examples
    $ remove-lockfiles
    $ remove-lockfiles ../foo
    $ remove-lockfiles --shrinkwrap
    $ remove-lockfiles --shrinkwrap ../foo

API

removeLockfiles([options])

Returns Promise<Array> of deleted lockfiles.

options

Type: Object

cwd

Type: string
Default: process.cwd()

Current working directory.

shrinkwrap

Type: boolean
Default: false

Set to true to remove npm-shrinkwrap.json.

del-nm-cli － Delete node_modules and lockfiles
force-del － Force delete files or folders using glob patterns
has-lockfile － Detect lockfiles in the working directory

License

MIT © Lufty Wiranda

remove-lockfiles's People

Contributors

Stargazers

Watchers

remove-lockfiles's Issues

An in-range update of force-del is breaking the build 🚨

Version 1.3.0 of force-del was just published.

Branch	Build failing 🚨
Dependency	force-del
Current Version	1.2.0
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

force-del is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 3 commits.

3d4035d 1.3.0
4b4ebd5 refactor: remove unnecessary leftovers (#10)
705ac6e refactor(del): use rimraf directly

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

Added the new Node.js version to your .travis.yml
The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

engines was only updated if it defined a single version, not a range.
.nvmrc was updated to Node.js 10
.travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of eslint-config-prettier is breaking the build 🚨

Version 2.5.0 of eslint-config-prettier just got published.

Branch	Build failing 🚨
Dependency	eslint-config-prettier
Current Version	2.4.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-config-prettier is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 4 commits.

1958386 eslint-config-prettier v2.5.0
23566d6 Add support for eslint-plugin-standard
9a78202 Make failing test-lint/ tests easier to understand
6feed44 Update dependencies

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of lint-staged is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 7.0.1 of lint-staged was just published.

Branch	Build failing 🚨
Dependency	lint-staged
Current Version	7.0.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

lint-staged is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes

v7.0.1

7.0.1 (2018-03-30)

Bug Fixes

package: update staged-git-files to version 1.1.1 (31176c9)

Commits

The new version differs by 6 commits.

3ea8b06 chore(package): update lockfile
31176c9 fix(package): update staged-git-files to version 1.1.1
19e39cd chore: Update prettier to the latest version 🚀 (#405)
7fa2fa6 docs: Move section for use with monorepo under FAQ (#409)
7cca081 docs: Add JetBrains IDE instructions for bugfix (#408)
ee024f8 chore(package): Update prettier to version 1.11.0 (#403)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of lint-staged is breaking the build 🚨

Version 7.2.0 of lint-staged was just published.

Branch	Build failing 🚨
Dependency	`lint-staged`
Current Version	7.1.3
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ continuous-integration/appveyor/branch AppVeyor build failed Details
✅ continuous-integration/travis-ci/push The Travis CI build passed Details

Release Notes

v7.2.0

7.2.0 (2018-06-11)

Features

Resolve a npm package passed as --config (#464) (c34a3f7)

Commits

The new version differs by 1 commits.

c34a3f7 feat: Resolve a npm package passed as --config (#464)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of all-contributors-cli is breaking the build 🚨

Version 4.9.0 of all-contributors-cli was just published.

Branch	Build failing 🚨
Dependency	all-contributors-cli
Current Version	4.8.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

all-contributors-cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes

v4.9.0

4.9.0 (2017-11-22)

Features

add prettier-ignore to output (#74) (ba248a9)

Commits

The new version differs by 3 commits.

ba248a9 feat: add prettier-ignore to output (#74)
482a8ab chore: upgrade and migrate tooling stuff (#73)
3d998c4 doc: credit @GantMan for his contributions

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of update-notifier is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.4.0 of update-notifier was just published.

Branch	Build failing 🚨
Dependency	update-notifier
Current Version	2.3.0
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

update-notifier is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 6 commits.

edbe3d2 2.4.0
83c4daa Add license file
accc884 Fix URI Scheme in package.json (#136)
0ad8e5b Update URL to XO
38d5679 Disable on CI (#116)
3e5cea0 Fix typo in README (#128)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of eslint-config-bunny is breaking the build 🚨

Version 5.1.0 of eslint-config-bunny just got published.

Branch	Build failing 🚨
Dependency	eslint-config-bunny
Current Version	5.0.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-config-bunny is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 3 commits.

248e848 v5.1.0
b7ffee2 DEPRECATE THIS PACKAGE
10b38d2 Update readme.md

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of update-notifier is breaking the build 🚨

The dependency update-notifier was updated from `2.5.0` to `2.6.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

update-notifier is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).

Commits

The new version differs by 10 commits.

622ee5f 2.6.0
ad8ed1b Suggest yarn when installed with yarn (#132)
5f06620 Exit the update check process if it does not respond after 30s (#156)
79e89ad Fix failing test (#155)
c8faa84 Add distTag option (#151)
14632e4 Add failing test for #153 (#154)
aafd8a0 Require Node.js 8
0d49f51 Add Tidelift mention in the readme
8df01b3 Fix docs position of shouldNotifyInNpmScript (#143)
d371834 Docs: isGlobal option does not default to true (#142)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of lint-staged is breaking the build 🚨

Version 4.2.0 of lint-staged just got published.

Branch	Build failing 🚨
Dependency	lint-staged
Current Version	4.1.3
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As lint-staged is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/appveyor/branch AppVeyor build failed Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

v4.2.0

4.2.0 (2017-09-15)

Features

Print friendlier error if config is missing (#281) (30fa594)

Commits

The new version differs by 8 commits.

30fa594 feat: Print friendlier error if config is missing (#281)
0077644 chore: Cleanup package.json (#250)
7abe23f ci: Disable email notifications from Travis CI
c9d0849 docs: Use emojis in the Readme
e976a3c docs: Add screenshot with the animated gif (#276)
92e586b docs: Reformat code blocks
9b0282a docs: Use diff formatting for code
33da9b3 ci: Whitelist build branches to avoid duplicate builds (#269)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

luftywiranda13 / remove-lockfiles Goto Github PK

remove-lockfiles's Introduction

remove-lockfiles

Why

Installation

Usage

Pre-commit hook

CLI

API

removeLockfiles([options])

options

cwd

shrinkwrap

Related

License

remove-lockfiles's People

Contributors

Stargazers

Watchers

remove-lockfiles's Issues

Version 1.3.0 of force-del was just published.

Version 10 of Node.js (code name Dubnium) has been released! 🎊

Version 2.5.0 of eslint-config-prettier just got published.

Version 7.0.1 of lint-staged was just published.

7.0.1 (2018-03-30)

Bug Fixes

Version 7.2.0 of lint-staged was just published.

7.2.0 (2018-06-11)

Features

Version 4.9.0 of all-contributors-cli was just published.

4.9.0 (2017-11-22)

Features

Version 2.4.0 of update-notifier was just published.

Version 5.1.0 of eslint-config-bunny just got published.

The dependency update-notifier was updated from 2.5.0 to 2.6.0.

Version 4.2.0 of lint-staged just got published.

4.2.0 (2017-09-15)

Features

Recommend Projects

Recommend Topics

Recommend Org

The dependency update-notifier was updated from `2.5.0` to `2.6.0`.