ca="-----BEGIN CERTIFICATE-----\nXXXX\nXXXX\n-----END CERTIFICATE-----"

ca[]="..."
ca[]="..."

cert="-----BEGIN CERTIFICATE-----\nXXXX\nXXXX\n-----END CERTIFICATE-----"

key="-----BEGIN PRIVATE KEY-----\nXXXX\nXXXX\n-----END PRIVATE KEY-----"

################# Dependency Hoisting Settings #################
################# https://pnpm.io/npmrc#dependency-hoisting-settings
# When true, all dependencies are hoisted to node_modules/.pnpm. This makes unlisted dependencies accessible to all packages inside node_modules.
hoist=true,
# Tells pnpm which packages should be hoisted to node_modules/.pnpm. By default, all packages are hoisted - however, if you know that only some flawed packages have phantom dependencies, you can use this option to exclusively hoist the phantom dependencies (recommended).
# hoist-pattern[]=*eslint*
# hoist-pattern[]=*babel*
hoist-pattern=['*']
# Unlike hoist-pattern, which hoists dependencies to a hidden modules directory inside the virtual store, public-hoist-pattern hoists dependencies matching the pattern to the root modules directory. Hoisting to the root modules directory means that application code will have access to phantom dependencies, even if they modify the resolution strategy improperly.
# string[]
# public-hoist-pattern[]=*plugin*
# public-hoist-pattern[]=*types*
# public-hoist-pattern[]=!@types/react
public-hoist-pattern=['*eslint*', '*prettier*']
# By default, pnpm creates a semistrict node_modules, meaning dependencies have access to undeclared dependencies but modules outside of node_modules do not. 
# With this layout, most of the packages in the ecosystem work with no issues.
# However, if some tooling only works when the hoisted dependencies are in the root of node_modules, you can set this to true to hoist them for you.
# Boolean
shamefully-hoist=false
################# Node-Modules Settings #################
################# https://pnpm.io/npmrc#node-modules-settings
# The location where all the packages are saved on the disk.
# The store should be always on the same disk on which installation is happening, so there will be one store per disk.
# If there is a home directory on the current disk, then the store is created inside it. If there is no home on the disk, then the store is created at the root of the filesystem.
# For example, if installation is happening on a filesystem mounted at /mnt, then the store will be created at /mnt/.pnpm-store. The same goes for Windows systems.
# It is possible to set a store from a different disk but in that case pnpm will copy packages from the store instead of hard-linking them, as hard links are only possible on the same filesystem.
store-dir=~/AppData/Local/pnpm/store
# The directory in which dependencies will be installed (instead of node_modules).
modules-dir=node_modules
# Defines what linker should be used for installing Node packages.
# Type: isolated, hoisted, pnp
# isolated - dependencies are symlinked from a virtual store at node_modules/.pnpm.
# hoisted - a flat node_modules without symlinks is created. Same as the node_modules created by npm or Yarn Classic. 
# pnp - no node_modules. Plug'n'Play is an innovative strategy for Node that is used by Yarn Berry. It is recommended to also set symlink setting to false when using pnp as your linker.
node-linker=isolated
# When symlink is set to false, pnpm creates a virtual store directory without any symlinks. It is a useful setting together with node-linker=pnp.
symlink=true
# When false, pnpm will not write any files to the modules directory (node_modules). This is useful for when the modules directory is mounted with filesystem in userspace (FUSE). 
# There is an experimental CLI that allows you to mount a modules directory with FUSE: @pnpm/mount-modules.
enable-modules-dir=true
# The directory with links to the store. All direct and indirect dependencies of the project are linked into this directory.
# This is a useful setting that can solve issues with long paths on Windows. 
# If you have some dependencies with very long paths, you can select a virtual store in the root of your drive (for instance C:\my-project-store).
# NOTE: the virtual store cannot be shared between several projects. Every project should have its own virtual store (except for in workspaces where the root is shared).
virtual-store-dir=node_modules/.pnpm
# Controls the way packages are imported from the store (if you want to disable symlinks inside node_modules, then you need to change the node-linker setting, not this one).
# Type: auto, hardlink, copy, clone, clone-or-copy
# auto - try to clone packages from the store. If cloning is not supported then hardlink packages from the store. If neither cloning nor linking is possible, fall back to copying
# hardlink - hard link packages from the store
# clone-or-copy - try to clone packages from the store. If cloning is not supported then fall back to copying
# copy - copy packages from the store
# clone - clone (AKA copy-on-write or reference link) packages from the store
package-import-method=auto
# The time in minutes after which orphan packages from the modules directory should be removed. pnpm keeps a cache of packages in the modules directory. 
# This boosts installation speed when switching branches or downgrading dependencies.
modules-cache-max-age=10080
################# Lockfile Settings #################
################# https://pnpm.io/npmrc#lockfile-settings
# When set to false, pnpm won't read or generate a pnpm-lock.yaml file.
lockfile=true
# When set to true and the available pnpm-lock.yaml satisfies the package.json dependencies directive, a headless installation is performed. A headless installation skips all dependency resolution as it does not need to modify the lockfile.
prefer-frozen-lockfile=true
# Add the full URL to the package's tarball to every entry in pnpm-lock.yaml.
lockfile-include-tarball-url=false
################# Registry & Authentication Settings #################
################# https://pnpm.io/npmrc#registry--authentication-settings
# The base URL of the npm package registry (trailing slash included).
# The npm registry that should be used for packages of the specified scope.
# For example, setting @babel:registry=https://example.com/packages/npm/ will enforce that when you use pnpm add @babel/core, or any @babel scoped package, the package will be fetched from https://example.com/packages/npm instead of the default registry.
registry=https://registry.npmjs.org/
################# Request Settings #################
################# https://pnpm.io/npmrc#request-settings
# The Certificate Authority signing certificate that is trusted for SSL connections to the registry.
# Values should be in PEM format (AKA "Base-64 encoded X.509 (.CER)"). For example:
# ca="-----BEGIN CERTIFICATE-----\nXXXX\nXXXX\n-----END CERTIFICATE-----"
# Set to null to only allow known registrars, or to a specific CA cert to trust only that specific signing authority.
# Multiple CAs can be trusted by specifying an array of certificates:
# ca[]="..."
# ca[]="..."
# Type: String, Array or null
# Default: The npm CA certificate
# See also the strict-ssl config.
# ca= null
# A path to a file containing one or multiple Certificate Authority signing certificates. 
# Similar to the ca setting, but allows for multiple CAs, as well as for the CA information to be stored in a file instead of being specified via CLI.
cafile =null
# A client certificate to pass when accessing the registry.
# Values should be in PEM format (AKA "Base-64 encoded X.509 (.CER)"). For example:
# cert="-----BEGIN CERTIFICATE-----\nXXXX\nXXXX\n-----END CERTIFICATE-----"
# It is not the path to a certificate file (and there is no certfile option).
cert=null
# A client key to pass when accessing the registry. 
# Values should be in PEM format (AKA "Base-64 encoded X.509 (.CER)"). For example:
# key="-----BEGIN PRIVATE KEY-----\nXXXX\nXXXX\n-----END PRIVATE KEY-----"
# It is not the path to a key file (and there is no keyfile option).
# This setting contains sensitive information. Don't write it to a local .npmrc file committed to the repository.
key=null
# When fetching dependencies that are Git repositories, if the host is listed in this setting, pnpm will use shallow cloning to fetch only the needed commit, not all the history.
# Type: string[]
git-shallow-hosts=['github.com', 'gist.github.com', 'gitlab.com', 'bitbucket.com', 'bitbucket.org']
# A proxy to use for outgoing HTTPS requests. If the HTTPS_PROXY, https_proxy, HTTP_PROXY or http_proxy environment variables are set, their values will be used instead.
https-proxy=null
# The IP address of the local interface to use when making connections to the npm registry.
# local-address=undefined
# A proxy to use for outgoing http requests. If the HTTP_PROXY or http_proxy environment variables are set, proxy settings will be honored by the underlying request library.
proxy=null
# The maximum number of connections to use per origin (protocol/host/port combination).
# Default: network-concurrency x 3
# maxsockets=3
# A comma-separated string of domain extensions that a proxy should not be used for.
noproxy=null
# Whether or not to do SSL key validation when making requests to the registry via HTTPS.
# Default: true
strict-ssl=true
# Controls the maximum number of HTTP(S) requests to process simultaneously.
# Default: 16
network-concurrency=16
# How many times to retry if pnpm fails to fetch from the registry.
# Default: 2
fetch-retries=2
# The exponential factor for retry backoff.
# Default: 10
fetch-retry-factor=10
# The minimum (base) timeout for retrying requests.
# Default: 10000 (10 seconds)
fetch-retry-mintimeout=10000
# The maximum fallback timeout to ensure the retry factor does not make requests too long.
# Default: 60000 (1 minute)
fetch-retry-maxtimeout=60000
# The maximum amount of time to wait for HTTP requests to complete.
# Default: 60000 (1 minute)
fetch-timeout=60000
################# Peer Dependency Settings #################
################# https://pnpm.io/npmrc#peer-dependency-settings
# When true, any missing non-optional peer dependencies are automatically installed.
# Default: false
auto-install-peers=false
# If this is enabled, commands will fail if there is a missing or invalid peer dependency in the tree.
# Default: false (was true from v7.0.0 until v7.13.5)
strict-peer-dependencies=false
################# CLI Settings #################
################# https://pnpm.io/npmrc#cli-settings
# Controls colors in the output.
# Default: auto
# Type: auto, always, never
# auto - output uses colors when the standard output is a terminal or TTY.
# always - ignore the difference between terminals and pipes. You’ll rarely want this; in most scenarios, if you want color codes in your redirected output, you can instead pass a --color flag to the pnpm command to force it to use color codes. The default setting is almost always what you’ll want.
# never - turns off colors. This is the setting used by --no-color.
color=auto
# Any logs at or higher than the given level will be shown. You can instead pass --silent to turn off all output logs.
# Default: info
# Type: debug, info, warn, error
loglevel=info
# Experimental option that enables beta features of the CLI. This means that you may get some changes to the CLI functionality that are breaking changes, or potentially bugs.
# Default: false
use-beta-cli=false
# If this is enabled, the primary behaviour of pnpm install becomes that of pnpm install -r, meaning the install is performed on all workspace or subdirectory packages.
# Else, pnpm install will exclusively build the package in the current directory.
# Default: true
recursive-install=true
# If this is enabled, pnpm will not install any package that claims to not be compatible with the current Node version.
# Regardless of this configuration, installation will always fail if a project (not a dependency) specifies an incompatible version in its engines field.
engine-strict=false
# The location of the npm binary that pnpm uses for some actions, like publishing.
# npm-path= 
################# Build Settings #################
################# https://pnpm.io/npmrc#nodejs-settings
# Do not execute any scripts defined in the project package.json and its dependencies.
# This flag does not prevent the execution of .pnpmfile.cjs
ignore-scripts=false
# Do not execute any scripts of the installed packages. Scripts of the projects are executed.
# Default: false
ignore-dep-scripts=false
# The maximum number of child processes to allocate simultaneously to build node_modules.
# Default: 5
child-concurrency=5
# Use and cache the results of (pre/post)install hooks.
# Default: true
side-effects-cache=true
# Only use the side effects cache if present, do not create it for new packages.
# Default: false
side-effects-cache-readonly=false
# Set to true to enable UID/GID switching when running package scripts. If set explicitly to false, then installing as a non-root user will fail.
# Default: false IF running as root, ELSE true
unsafe-perm=false
################# Node.js Settings #################
################# https://pnpm.io/npmrc#nodejs-settings
# Specifies which exact Node.js version should be used for the project's runtime. 
# pnpm will automatically install the specified version of Node.js and use it for running pnpm run commands or the pnpm node command.
# This may be used instead of .nvmrc and nvm. Instead of the following .nvmrc file:
# Type: semver
# Default: undefined
# use-node-version=19.2.0
# If you want to prevent contributors of your project from adding new incompatible dependencies, use node-version and engine-strict in a .npmrc file at the root of the project
# Type: semver
# Default: the value returned by node -v, without the v prefix
node-version=19.2.0
# Sets the base URL for downloading Node.js.
# he <releaseDir> portion of this setting can be any directory from https://nodejs.org/download: release, rc, nightly, v8-canary, etc.
node-mirror=https://nodejs.org/download/release/
################# Workspace Settings #################
################# https://pnpm.io/npmrc#workspace-settings
# If this is enabled, locally available packages are linked to node_modules instead of being downloaded from the registry. This is very convenient in a monorepo. If you need local packages to also be linked to subdependencies, you can use the deep setting.
# Else, packages are downloaded and installed from the registry. However, workspace packages can still be linked by using the workspace: range protocol.
# Type: true, false, deep
link-workspace-packages=true
# If this is enabled, local packages from the workspace are preferred over packages from the registry, even if there is a newer version of the package in the registry.
# Default: false
prefer-workspace-packages=false
# If this is enabled, pnpm creates a single pnpm-lock.yaml file in the root of the workspace.
# This also means that all dependencies of workspace packages will be in a single node_modules (and get symlinked to their package node_modules folder for Node's module resolution).
# Default: true
shared-workspace-lockfile=true
# This setting controls how dependencies that are linked from the workspace are added to package.json.
# If foo@1.0.0 is in the workspace and you run pnpm add foo in another project of the workspace, below is how foo will be added to the dependencies field. 
# The save-prefix setting also influences how the spec is created.
# Default: true
# Type: true, false, rolling
# https://pnpm.io/npmrc#save-workspace-protocol
save-workspace-protocol=true
# When executing commands recursively in a workspace, execute them on the root workspace project as well.
# Default: false
include-workspace-root=flase
################# Other Settings #################
################# https://pnpm.io/npmrc#other-settings
use-running-store-server=false
# Configure how versions of packages installed to a package.json file get prefixed.
# For example, if a package has version 1.2.3, by default its version is set to ^1.2.3 which allows minor upgrades for that package, but after pnpm config set save-prefix='~' it would be set to ~1.2.3 which only allows patch upgrades.
# This setting is ignored when the added package has a range specified. 
# For instance, pnpm add foo@2 will set the version of foo in package.json to 2, regardless of the value of save-prefix.
save-prefix=^
# If you pnpm add a package and you don't provide a specific version, then it will install the package at the version registered under the tag from this setting.
# This also sets the tag that is added to the package@version specified by the pnpm tag command if no explicit tag is given.
# Default: latest
# Specify a custom directory to store global packages.
tag=latest
global-dir=~/AppData/Local/pnpm/global
# Allows to set the target directory for the bin files of globally installed packages.
global-bin-dir=~/AppData/Local/pnpm
# The directory where pnpm creates the pnpm-state.json file that is currently used only by the update checker.
state-dir=~/AppData/Local/pnpm-state
# The location of the package metadata cache.
cache-dir=~/AppData/Local/pnpm-cache
# When true, all the output is written to stderr.
# Default: false
use-stderr=false
# Set to false to suppress the update notification when using an older version of pnpm than the latest.
# Default: true
update-notifier=true
# Create symlinks to executables in node_modules/.bin instead of command shims.
# This setting is ignored on Windows, where only command shims work.
# Default: true, when node-linker is set to hoisted and the system is POSIX
prefer-symlinked-executables=true
# By default, if a file in the store has been modified, the content of this file is checked before linking it to a project's node_modules.
# If verify-store-integrity is set to false, files in the content-addressable store will not be checked during installation.
# Default: true
verify-store-integrity=true
# During installation the dependencies of some packages are automatically patched. If you want to disable this, set this config to false.
# The patches are applied from Yarn's @yarnpkg/extensions package.
# Default: false
ignore-compatibility-db=false
# When resolution-mode is set to time-based, dependencies will be resolved the following way:
# - Direct dependencies will be resolved to their lowest versions. So if there is foo@^1.1.0 in the dependencies, then 1.1.0 will be installed.
# - Subdependencies will be resolved from versions that were published before the last direct dependency was published.
# With this resolution mode installations with warm cache are faster.
# It also reduces the chance of subdependency hijacking as subdependencies will be updated only if direct dependencies are updated.
# This resolution mode works only with npm's full metadata. 
# So it is slower in some scenarios. However, if you use Verdaccio v5.15.1 or newer, you may set the registry-supports-time-field setting to true, and it will be really fast.
# Type: highest, time-based
# Default: highest
resolution-mode=highest
# Set this to true if the registry that you are using returns the "time" field in the abbreviated metadata.
# As of now, only Verdaccio from v5.15.1 supports this.
# Default: false
registry-supports-time-field=false