hops-config
Advanced tools
Comparing version 7.0.0-0 to 7.0.0-3
{ | ||
"name": "hops-config", | ||
"version": "7.0.0-0", | ||
"version": "7.0.0-3", | ||
"description": "Hops core configuration", | ||
@@ -5,0 +5,0 @@ "keywords": [ |
@@ -6,5 +6,6 @@ # Hops Config | ||
# Installation | ||
When you use any of the other hops packages, it is highly likely that you need to install `hops-config` as a peerDependency yourself. | ||
Please have a look at the package.json files of the other hops packages that you use or check your npm/yarn logs to see if you need to install hops-config as a peerDependency. | ||
In case you want to extend the configuration or access it from your server/browser code, you should explicitly add `hops-config` as a dependency to your project. | ||
Otherwise it will be installed through the other hops packages and doesn't need to be installed directly. | ||
``` | ||
@@ -36,3 +37,3 @@ npm install --save hops-config | ||
Everything matching `/(config|file|dir)s?$/i` will be treated as a filesystem path (or array thereof) and resolved relative to your app's root folder. This only applies if the respective value is not an absolute path already. | ||
All keys matching `/(config|file|dir)s?$/i` will be treated as a filesystem path (or array thereof) and resolved relative to your app's root folder. This only applies if the respective value is not an absolute path already. | ||
@@ -39,0 +40,0 @@ ## Configure via package.json |
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
96
0
10759