This commit is contained in:
2022-07-18 02:50:52 +00:00
parent befd344ab0
commit 06181b34d6
8569 changed files with 818704 additions and 352705 deletions
+10
View File
@@ -2,6 +2,16 @@
All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
<a name="4.1.2"></a>
## [4.1.2](https://github.com/moxystudio/node-proper-lockfile/compare/v4.1.1...v4.1.2) (2021-01-25)
### Bug Fixes
* fix node 14 updating graceful-fs ([#102](https://github.com/moxystudio/node-proper-lockfile/issues/102)) ([b0d988e](https://github.com/moxystudio/node-proper-lockfile/commit/b0d988e))
<a name="4.1.1"></a>
## [4.1.1](https://github.com/moxystudio/node-proper-lockfile/compare/v4.1.0...v4.1.1) (2019-04-03)
+9 -9
View File
@@ -3,10 +3,10 @@
[![NPM version][npm-image]][npm-url] [![Downloads][downloads-image]][npm-url] [![Build Status][travis-image]][travis-url] [![Coverage Status][codecov-image]][codecov-url] [![Dependency status][david-dm-image]][david-dm-url] [![Dev Dependency status][david-dm-dev-image]][david-dm-dev-url]
[npm-url]:https://npmjs.org/package/proper-lockfile
[downloads-image]:http://img.shields.io/npm/dm/proper-lockfile.svg
[npm-image]:http://img.shields.io/npm/v/proper-lockfile.svg
[downloads-image]:https://img.shields.io/npm/dm/proper-lockfile.svg
[npm-image]:https://img.shields.io/npm/v/proper-lockfile.svg
[travis-url]:https://travis-ci.org/moxystudio/node-proper-lockfile
[travis-image]:http://img.shields.io/travis/moxystudio/node-proper-lockfile/master.svg
[travis-image]:https://img.shields.io/travis/moxystudio/node-proper-lockfile/master.svg
[codecov-url]:https://codecov.io/gh/moxystudio/node-proper-lockfile
[codecov-image]:https://img.shields.io/codecov/c/github/moxystudio/node-proper-lockfile/master.svg
[david-dm-url]:https://david-dm.org/moxystudio/node-proper-lockfile
@@ -34,7 +34,7 @@ When a lock is successfully acquired, the lockfile's `mtime` (modified time) is
### Comparison
This library is similar to [lockfile](https://github.com/isaacs/lockfile) but the later has some drawbacks:
This library is similar to [lockfile](https://github.com/isaacs/lockfile) but the latter has some drawbacks:
- It relies on `open` with `O_EXCL` flag which has problems in network file systems. `proper-lockfile` uses `mkdir` which doesn't have this issue.
@@ -42,7 +42,7 @@ This library is similar to [lockfile](https://github.com/isaacs/lockfile) but th
- The lockfile staleness check is done via `ctime` (creation time) which is unsuitable for long running processes. `proper-lockfile` constantly updates lockfiles `mtime` to do proper staleness check.
- It does not check if the lockfile was compromised which can led to undesirable situations. `proper-lockfile` checks the lockfile when updating the `mtime`.
- It does not check if the lockfile was compromised which can lead to undesirable situations. `proper-lockfile` checks the lockfile when updating the `mtime`.
- It has a default value of `0` for the stale option which isn't good because any crash or process kill that the package can't handle gracefully will leave the lock active forever.
@@ -57,7 +57,7 @@ This library is similar to [lockfile](https://github.com/isaacs/lockfile) but th
`proper-lockfile` detects cases in which:
- Updates to the `lockfile` fail
- Updates take longer than expected, possibly causing the lock to became stale for a certain amount of time
- Updates take longer than expected, possibly causing the lock to become stale for a certain amount of time
As you see, the first two are a consequence of bad usage. Technically, it was possible to detect the first two but it would introduce complexity and eventual race conditions.
@@ -107,7 +107,7 @@ lockfile.lock('some/file')
Releases a previously acquired lock on `file` or rejects the promise on error.
Whenever possible you should use the `release` function instead (as exemplified above). Still there are cases in which its hard to keep a reference to it around code. In those cases `unlock()` might be handy.
Whenever possible you should use the `release` function instead (as exemplified above). Still there are cases in which it's hard to keep a reference to it around code. In those cases `unlock()` might be handy.
Available options:
@@ -167,7 +167,7 @@ Returns a boolean or throws on error.
## Graceful exit
`proper-lockfile` automatically remove locks if the process exists, except if the process is killed with SIGKILL or it crashes due to a VM fatal error (e.g.: out of memory).
`proper-lockfile` automatically removes locks if the process exits, except if the process is killed with SIGKILL or it crashes due to a VM fatal error (e.g.: out of memory).
## Tests
@@ -180,4 +180,4 @@ The test suite is very extensive. There's even a stress test to guarantee exclus
## License
Released under the [MIT License](http://www.opensource.org/licenses/mit-license.php).
Released under the [MIT License](https://www.opensource.org/licenses/mit-license.php).
+15 -19
View File
@@ -1,32 +1,32 @@
{
"_args": [
[
"proper-lockfile@4.1.1",
"/mnt/Foxconn/Digitalent/Deverloper/liff-push_2series"
"proper-lockfile@4.1.2",
"/home/node/nuxt"
]
],
"_from": "proper-lockfile@4.1.1",
"_id": "proper-lockfile@4.1.1",
"_from": "proper-lockfile@4.1.2",
"_id": "proper-lockfile@4.1.2",
"_inBundle": false,
"_integrity": "sha512-1w6rxXodisVpn7QYvLk706mzprPTAPCYAqxMvctmPN3ekuRk/kuGkGc82pangZiAt4R3lwSuUzheTTn0/Yb7Zg==",
"_integrity": "sha512-TjNPblN4BwAWMXU8s9AEz4JmQxnD1NNL7bNOY/AKUzyamc379FWASUhc/K1pL2noVb+XmZKLL68cjzLsiOAMaA==",
"_location": "/proper-lockfile",
"_phantomChildren": {},
"_requested": {
"type": "version",
"registry": true,
"raw": "proper-lockfile@4.1.1",
"raw": "proper-lockfile@4.1.2",
"name": "proper-lockfile",
"escapedName": "proper-lockfile",
"rawSpec": "4.1.1",
"rawSpec": "4.1.2",
"saveSpec": null,
"fetchSpec": "4.1.1"
"fetchSpec": "4.1.2"
},
"_requiredBy": [
"/@nuxt/utils"
],
"_resolved": "https://registry.npmjs.org/proper-lockfile/-/proper-lockfile-4.1.1.tgz",
"_spec": "4.1.1",
"_where": "/mnt/Foxconn/Digitalent/Deverloper/liff-push_2series",
"_resolved": "https://registry.npmjs.org/proper-lockfile/-/proper-lockfile-4.1.2.tgz",
"_spec": "4.1.2",
"_where": "/home/node/nuxt",
"author": {
"name": "André Cruz",
"email": "andre@moxy.studio"
@@ -40,7 +40,7 @@
]
},
"dependencies": {
"graceful-fs": "^4.1.11",
"graceful-fs": "^4.2.4",
"retry": "^0.12.0",
"signal-exit": "^3.0.2"
},
@@ -57,7 +57,7 @@
"jest": "^24.5.0",
"lint-staged": "^8.0.4",
"mkdirp": "^0.5.1",
"p-defer": "^1.0.0",
"p-defer": "^2.1.0",
"rimraf": "^2.6.2",
"stable": "^0.1.8",
"standard-version": "^5.0.0",
@@ -96,14 +96,10 @@
},
"scripts": {
"lint": "eslint .",
"postrelease": "git push --follow-tags origin HEAD && npm publish",
"prerelease": "npm t && npm run lint",
"release": "standard-version",
"test": "jest --env node --coverage --runInBand"
},
"standard-version": {
"scripts": {
"posttag": "git push --follow-tags origin master"
}
},
"version": "4.1.1"
"version": "4.1.2"
}