@jsenv/monorepo 0.0.4 → 0.0.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +6 -6
  2. package/readme.md +2 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jsenv/monorepo",
3
- "version": "0.0.4",
3
+ "version": "0.0.5",
4
4
  "description": "Helpers to manage packages in a monorepo",
5
5
  "license": "MIT",
6
6
  "author": {
@@ -34,10 +34,10 @@
34
34
  "test": "node ./scripts/test.mjs"
35
35
  },
36
36
  "dependencies": {
37
- "@jsenv/urls": "2.2.1",
38
- "@jsenv/filesystem": "4.3.2",
39
- "@jsenv/package-publish": "1.10.4",
40
- "@jsenv/log": "3.4.2",
41
- "semver": "7.5.4"
37
+ "@jsenv/urls": "2.2.4",
38
+ "@jsenv/filesystem": "4.6.6",
39
+ "@jsenv/package-publish": "1.10.5",
40
+ "@jsenv/log": "3.5.2",
41
+ "semver": "7.6.2"
42
42
  }
43
43
  }
package/readme.md CHANGED
@@ -134,7 +134,8 @@ Most of the time you don't want to update your deps. The 2 most common scenarios
134
134
 
135
135
  "I want to update all my deps" happens from time to time but is usually not what you had in mind before executing "npm install"
136
136
 
137
- Moreover the usage of _package-lock.json_ remains optional.
137
+ Moreover the usage of _package-lock.json_ remains optional.
138
+ And _package-lock.json_ can be problematic https://github.com/npm/cli/issues/4828, some project disable package-lock to avoid these kind of issues until the situation becomes better.
138
139
 
139
140
  ## How to avoid the problem
140
141