@dotenvx/next-env 1.74.3 → 2.0.1

package/node_modules/conf/readme.md

@@ -1,445 +0,0 @@
-# conf
-
-> Simple config handling for your app or module
-
-All you have to care about is what to persist. This module will handle all the dull details like where and how.
-
-**It does not support multiple processes writing to the same store.**\
-I initially made this tool to let command-line tools persist some data.
-
-*If you need this for Electron, check out [`electron-store`](https://github.com/sindresorhus/electron-store) instead.*
-
-## Install
-
-```
-$ npm install conf
-```
-
-## Usage
-
-```js
-const Conf = require('conf');
-
-const config = new Conf();
-
-config.set('unicorn', '🦄');
-console.log(config.get('unicorn'));
-//=> '🦄'
-
-// Use dot-notation to access nested properties
-config.set('foo.bar', true);
-console.log(config.get('foo'));
-//=> {bar: true}
-
-config.delete('unicorn');
-console.log(config.get('unicorn'));
-//=> undefined
-```
-
-Or [create a subclass](https://github.com/sindresorhus/electron-store/blob/main/index.js).
-
-## API
-
-Changes are written to disk atomically, so if the process crashes during a write, it will not corrupt the existing config.
-
-### Conf(options?)
-
-Returns a new instance.
-
-### options
-
-Type: `object`
-
-#### defaults
-
-Type: `object`
-
-Default values for the config items.
-
-**Note:** The values in `defaults` will overwrite the `default` key in the `schema` option.
-
-#### schema
-
-Type: `object`
-
-[JSON Schema](https://json-schema.org) to validate your config data.
-
-Under the hood, the JSON Schema validator [ajv](https://github.com/epoberezkin/ajv) is used to validate your config. We use [JSON Schema draft-07](https://json-schema.org/latest/json-schema-validation.html) and support all [validation keywords](https://github.com/epoberezkin/ajv/blob/master/KEYWORDS.md) and [formats](https://github.com/epoberezkin/ajv#formats).
-
-You should define your schema as an object where each key is the name of your data's property and each value is a JSON schema used to validate that property. See more [here](https://json-schema.org/understanding-json-schema/reference/object.html#properties).
-
-Example:
-
-```js
-const Conf = require('conf');
-
-const schema = {
-	foo: {
-		type: 'number',
-		maximum: 100,
-		minimum: 1,
-		default: 50
-	},
-	bar: {
-		type: 'string',
-		format: 'url'
-	}
-};
-
-const config = new Conf({schema});
-
-console.log(config.get('foo'));
-//=> 50
-
-config.set('foo', '1');
-// [Error: Config schema violation: `foo` should be number]
-```
-
-**Note:** The `default` value will be overwritten by the `defaults` option if set.
-
-### migrations
-
-Type: `object`
-
-You can use migrations to perform operations to the store whenever a **project version** is upgraded.
-
-The `migrations` object should consist of a key-value pair of `'version': handler`. The `version` can also be a [semver range](https://github.com/npm/node-semver#ranges).
-
-Example:
-
-```js
-const Conf = require('conf');
-
-const store = new Conf({
-	migrations: {
-		'0.0.1': store => {
-			store.set('debugPhase', true);
-		},
-		'1.0.0': store => {
-			store.delete('debugPhase');
-			store.set('phase', '1.0.0');
-		},
-		'1.0.2': store => {
-			store.set('phase', '1.0.2');
-		},
-		'>=2.0.0': store => {
-			store.set('phase', '>=2.0.0');
-		}
-	}
-});
-```
-
-> Note: The version the migrations use refers to the **project version** by default. If you want to change this behavior, specify the [`projectVersion`](#projectVersion) option.
-
-### beforeEachMigration
-
-Type: `Function`\
-Default: `undefined`
-
-The given callback function will be called before each migration step.
-
-The function receives the store as the first argument and a context object as the second argument with the following properties:
-
-- `fromVersion` - The version the migration step is being migrated from.
-- `toVersion` - The version the migration step is being migrated to.
-- `finalVersion` - The final version after all the migrations are applied.
-- `versions` - All the versions with a migration step.
-
-This can be useful for logging purposes, preparing migration data, etc.
-
-Example:
-
-```js
-const Conf = require('conf');
-
-console.log = someLogger.log;
-
-const mainConfig = new Conf({
-	beforeEachMigration: (store, context) => {
-		console.log(`[main-config] migrate from ${context.fromVersion} → ${context.toVersion}`);
-	},
-	migrations: {
-		'0.4.0': store => {
-			store.set('debugPhase', true);
-		},
-	}
-});
-
-const secondConfig = new Conf({
-	beforeEachMigration: (store, context) => {
-		console.log(`[second-config] migrate from ${context.fromVersion} → ${context.toVersion}`);
-	},
-	migrations: {
-		'1.0.1': store => {
-			store.set('debugPhase', true);
-		},
-	}
-});
-```
-
-#### configName
-
-Type: `string`\
-Default: `'config'`
-
-Name of the config file (without extension).
-
-Useful if you need multiple config files for your app or module. For example, different config files between two major versions.
-
-#### projectName
-
-Type: `string`\
-Default: The `name` field in the package.json closest to where `conf` is imported.
-
-You only need to specify this if you don't have a package.json file in your project or if it doesn't have a name defined within it.
-
-#### projectVersion
-
-Type: `string`\
-Default: The `version` field in the package.json closest to where `conf` is imported.
-
-You only need to specify this if you don't have a package.json file in your project or if it doesn't have a version defined within it.
-
-#### cwd
-
-Type: `string`\
-Default: System default [user config directory](https://github.com/sindresorhus/env-paths#pathsconfig)
-
-**You most likely don't need this. Please don't use it unless you really have to. By default, it will pick the optimal location by adhering to system conventions. You are very likely to get this wrong and annoy users.**
-
-Overrides `projectName`.
-
-The only use-case I can think of is having the config located in the app directory or on some external storage.
-
-#### encryptionKey
-
-Type: `string | Buffer | TypedArray | DataView`\
-Default: `undefined`
-
-Note that this is **not intended for security purposes**, since the encryption key would be easily found inside a plain-text Node.js app.
-
-Its main use is for obscurity. If a user looks through the config directory and finds the config file, since it's just a JSON file, they may be tempted to modify it. By providing an encryption key, the file will be obfuscated, which should hopefully deter any users from doing so.
-
-When specified, the store will be encrypted using the [`aes-256-cbc`](https://en.wikipedia.org/wiki/Block_cipher_mode_of_operation) encryption algorithm.
-
-#### fileExtension
-
-Type: `string`\
-Default: `'json'`
-
-Extension of the config file.
-
-You would usually not need this, but could be useful if you want to interact with a file with a custom file extension that can be associated with your app. These might be simple save/export/preference files that are intended to be shareable or saved outside of the app.
-
-#### clearInvalidConfig
-
-Type: `boolean`\
-Default: `false`
-
-The config is cleared if reading the config file causes a `SyntaxError`. This is a good behavior for unimportant data, as the config file is not intended to be hand-edited, so it usually means the config is corrupt and there's nothing the user can do about it anyway. However, if you let the user edit the config file directly, mistakes might happen and it could be more useful to throw an error when the config is invalid instead of clearing.
-
-#### serialize
-
-Type: `Function`\
-Default: `value => JSON.stringify(value, null, '\t')`
-
-Function to serialize the config object to a UTF-8 string when writing the config file.
-
-You would usually not need this, but it could be useful if you want to use a format other than JSON.
-
-#### deserialize
-
-Type: `Function`\
-Default: `JSON.parse`
-
-Function to deserialize the config object from a UTF-8 string when reading the config file.
-
-You would usually not need this, but it could be useful if you want to use a format other than JSON.
-
-#### projectSuffix
-
-Type: `string`\
-Default: `'nodejs'`
-
-**You most likely don't need this. Please don't use it unless you really have to.**
-
-Suffix appended to `projectName` during config file creation to avoid name conflicts with native apps.
-
-You can pass an empty string to remove the suffix.
-
-For example, on macOS, the config file will be stored in the `~/Library/Preferences/foo-nodejs` directory, where `foo` is the `projectName`.
-
-#### accessPropertiesByDotNotation
-
-Type: `boolean`\
-Default: `true`
-
-Accessing nested properties by dot notation. For example:
-
-```js
-const Conf = require('conf');
-
-const config = new Conf();
-
-config.set({
-	foo: {
-		bar: {
-			foobar: '🦄'
-		}
-	}
-});
-
-console.log(config.get('foo.bar.foobar'));
-//=> '🦄'
-```
-
-Alternatively, you can set this option to `false` so the whole string would be treated as one key.
-
-```js
-const Conf = require('conf');
-
-const config = new Conf({accessPropertiesByDotNotation: false});
-
-config.set({
-	`foo.bar.foobar`: '🦄'
-});
-
-console.log(config.get('foo.bar.foobar'));
-//=> '🦄'
-```
-
-#### watch
-
-type: `boolean`\
-Default: `false`
-
-Watch for any changes in the config file and call the callback for `onDidChange` or `onDidAnyChange` if set. This is useful if there are multiple processes changing the same config file.
-
-#### configFileMode
-
-Type: `number`\
-Default: `0o666`
-
-The [mode](https://en.wikipedia.org/wiki/File-system_permissions#Numeric_notation) that will be used for the config file.
-
-You would usually not need this, but it could be useful if you want to restrict the permissions of the config file. Setting a permission such as `0o600` would result in a config file that can only be accessed by the user running the program.
-
-Note that setting restrictive permissions can cause problems if different users need to read the file. A common problem is a user running your tool with and without `sudo` and then not being able to access the config the second time.
-
-### Instance
-
-You can use [dot-notation](https://github.com/sindresorhus/dot-prop) in a `key` to access nested properties.
-
-The instance is [`iterable`](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Iteration_protocols) so you can use it directly in a [`for…of`](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Statements/for...of) loop.
-
-#### .set(key, value)
-
-Set an item.
-
-The `value` must be JSON serializable. Trying to set the type `undefined`, `function`, or `symbol` will result in a TypeError.
-
-#### .set(object)
-
-Set multiple items at once.
-
-#### .get(key, defaultValue?)
-
-Get an item or `defaultValue` if the item does not exist.
-
-#### .reset(...keys)
-
-Reset items to their default values, as defined by the `defaults` or `schema` option.
-
-Use `.clear()` to reset all items.
-
-#### .has(key)
-
-Check if an item exists.
-
-#### .delete(key)
-
-Delete an item.
-
-#### .clear()
-
-Delete all items.
-
-This resets known items to their default values, if defined by the `defaults` or `schema` option.
-
-#### .onDidChange(key, callback)
-
-`callback`: `(newValue, oldValue) => {}`
-
-Watches the given `key`, calling `callback` on any changes.
-
-When a key is first set `oldValue` will be `undefined`, and when a key is deleted `newValue` will be `undefined`.
-
-Returns a function which you can use to unsubscribe:
-
-```js
-const unsubscribe = conf.onDidChange(key, callback);
-
-unsubscribe();
-```
-
-#### .onDidAnyChange(callback)
-
-`callback`: `(newValue, oldValue) => {}`
-
-Watches the whole config object, calling `callback` on any changes.
-
-`oldValue` and `newValue` will be the config object before and after the change, respectively. You must compare `oldValue` to `newValue` to find out what changed.
-
-Returns a function which you can use to unsubscribe:
-
-```js
-const unsubscribe = conf.onDidAnyChange(callback);
-
-unsubscribe();
-```
-
-#### .size
-
-Get the item count.
-
-#### .store
-
-Get all the config as an object or replace the current config with an object:
-
-```js
-conf.store = {
-	hello: 'world'
-};
-```
-
-#### .path
-
-Get the path to the config file.
-
-## FAQ
-
-### How is this different from [`configstore`](https://github.com/yeoman/configstore)?
-
-I'm also the author of `configstore`. While it's pretty good, I did make some mistakes early on that are hard to change at this point. This module is the result of everything I learned from making `configstore`. Mainly where the config is stored. In `configstore`, the config is stored in `~/.config` (which is mainly a Linux convention) on all systems, while `conf` stores config in the system default [user config directory](https://github.com/sindresorhus/env-paths#pathsconfig). The `~/.config` directory, it turns out, often have an incorrect permission on macOS and Windows, which has caused a lot of grief for users.
-
-### Can I use YAML or another serialization format?
-
-The `serialize` and `deserialize` options can be used to customize the format of the config file, as long as the representation is compatible with `utf8` encoding.
-
-Example using YAML:
-
-```js
-const Conf = require('conf');
-const yaml = require('js-yaml');
-
-const config = new Conf({
-	fileExtension: 'yaml',
-	serialize: yaml.safeDump,
-	deserialize: yaml.safeLoad
-});
-```
-
-## Related
-
-- [electron-store](https://github.com/sindresorhus/electron-store) - Simple data persistence for your Electron app or module
-- [cache-conf](https://github.com/SamVerschueren/cache-conf) - Simple cache config handling for your app or module

package/node_modules/cross-spawn/LICENSE

@@ -1,21 +0,0 @@
-The MIT License (MIT)
-
-Copyright (c) 2018 Made With MOXY Lda <hello@moxy.studio>
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.

package/node_modules/cross-spawn/README.md

@@ -1,89 +0,0 @@
-# cross-spawn
-
-[![NPM version][npm-image]][npm-url] [![Downloads][downloads-image]][npm-url] [![Build Status][ci-image]][ci-url] [![Build status][appveyor-image]][appveyor-url]
-
-[npm-url]:https://npmjs.org/package/cross-spawn
-[downloads-image]:https://img.shields.io/npm/dm/cross-spawn.svg
-[npm-image]:https://img.shields.io/npm/v/cross-spawn.svg
-[ci-url]:https://github.com/moxystudio/node-cross-spawn/actions/workflows/ci.yaml
-[ci-image]:https://github.com/moxystudio/node-cross-spawn/actions/workflows/ci.yaml/badge.svg
-[appveyor-url]:https://ci.appveyor.com/project/satazor/node-cross-spawn
-[appveyor-image]:https://img.shields.io/appveyor/ci/satazor/node-cross-spawn/master.svg
-
-A cross platform solution to node's spawn and spawnSync.
-
-## Installation
-
-Node.js version 8 and up:
-`$ npm install cross-spawn`
-
-Node.js version 7 and under:
-`$ npm install cross-spawn@6`
-
-## Why
-
-Node has issues when using spawn on Windows:
-
-- It ignores [PATHEXT](https://github.com/joyent/node/issues/2318)
-- It does not support [shebangs](https://en.wikipedia.org/wiki/Shebang_(Unix))
-- Has problems running commands with [spaces](https://github.com/nodejs/node/issues/7367)
-- Has problems running commands with posix relative paths (e.g.: `./my-folder/my-executable`)
-- Has an [issue](https://github.com/moxystudio/node-cross-spawn/issues/82) with command shims (files in `node_modules/.bin/`), where arguments with quotes and parenthesis would result in [invalid syntax error](https://github.com/moxystudio/node-cross-spawn/blob/e77b8f22a416db46b6196767bcd35601d7e11d54/test/index.test.js#L149)
-- No `options.shell` support on node `<v4.8`
-
-All these issues are handled correctly by `cross-spawn`.
-There are some known modules, such as [win-spawn](https://github.com/ForbesLindesay/win-spawn), that try to solve this but they are either broken or provide faulty escaping of shell arguments.
-
-
-## Usage
-
-Exactly the same way as node's [`spawn`](https://nodejs.org/api/child_process.html#child_process_child_process_spawn_command_args_options) or [`spawnSync`](https://nodejs.org/api/child_process.html#child_process_child_process_spawnsync_command_args_options), so it's a drop in replacement.
-
-
-```js
-const spawn = require('cross-spawn');
-
-// Spawn NPM asynchronously
-const child = spawn('npm', ['list', '-g', '-depth', '0'], { stdio: 'inherit' });
-
-// Spawn NPM synchronously
-const result = spawn.sync('npm', ['list', '-g', '-depth', '0'], { stdio: 'inherit' });
-```
-
-
-## Caveats
-
-### Using `options.shell` as an alternative to `cross-spawn`
-
-Starting from node `v4.8`, `spawn` has a `shell` option that allows you run commands from within a shell. This new option solves
-the [PATHEXT](https://github.com/joyent/node/issues/2318) issue but:
-
-- It's not supported in node `<v4.8`
-- You must manually escape the command and arguments which is very error prone, specially when passing user input
-- There are a lot of other unresolved issues from the [Why](#why) section that you must take into account
-
-If you are using the `shell` option to spawn a command in a cross platform way, consider using `cross-spawn` instead. You have been warned.
-
-### `options.shell` support
-
-While `cross-spawn` adds support for `options.shell` in node `<v4.8`, all of its enhancements are disabled.
-
-This mimics the Node.js behavior. More specifically, the command and its arguments will not be automatically escaped nor shebang support will be offered. This is by design because if you are using `options.shell` you are probably targeting a specific platform anyway and you don't want things to get into your way.
-
-### Shebangs support
-
-While `cross-spawn` handles shebangs on Windows, its support is limited. More specifically, it just supports `#!/usr/bin/env <program>` where `<program>` must not contain any arguments.   
-If you would like to have the shebang support improved, feel free to contribute via a pull-request.
-
-Remember to always test your code on Windows!
-
-
-## Tests
-
-`$ npm test`   
-`$ npm test -- --watch` during development
-
-
-## License
-
-Released under the [MIT License](https://www.opensource.org/licenses/mit-license.php).

package/node_modules/cross-spawn/index.js

@@ -1,39 +0,0 @@
-'use strict';
-
-const cp = require('child_process');
-const parse = require('./lib/parse');
-const enoent = require('./lib/enoent');
-
-function spawn(command, args, options) {
-    // Parse the arguments
-    const parsed = parse(command, args, options);
-
-    // Spawn the child process
-    const spawned = cp.spawn(parsed.command, parsed.args, parsed.options);
-
-    // Hook into child process "exit" event to emit an error if the command
-    // does not exists, see: https://github.com/IndigoUnited/node-cross-spawn/issues/16
-    enoent.hookChildProcess(spawned, parsed);
-
-    return spawned;
-}
-
-function spawnSync(command, args, options) {
-    // Parse the arguments
-    const parsed = parse(command, args, options);
-
-    // Spawn the child process
-    const result = cp.spawnSync(parsed.command, parsed.args, parsed.options);
-
-    // Analyze if the command does not exist, see: https://github.com/IndigoUnited/node-cross-spawn/issues/16
-    result.error = result.error || enoent.verifyENOENTSync(result.status, parsed);
-
-    return result;
-}
-
-module.exports = spawn;
-module.exports.spawn = spawn;
-module.exports.sync = spawnSync;
-
-module.exports._parse = parse;
-module.exports._enoent = enoent;

package/node_modules/cross-spawn/lib/enoent.js

@@ -1,59 +0,0 @@
-'use strict';
-
-const isWin = process.platform === 'win32';
-
-function notFoundError(original, syscall) {
-    return Object.assign(new Error(`${syscall} ${original.command} ENOENT`), {
-        code: 'ENOENT',
-        errno: 'ENOENT',
-        syscall: `${syscall} ${original.command}`,
-        path: original.command,
-        spawnargs: original.args,
-    });
-}
-
-function hookChildProcess(cp, parsed) {
-    if (!isWin) {
-        return;
-    }
-
-    const originalEmit = cp.emit;
-
-    cp.emit = function (name, arg1) {
-        // If emitting "exit" event and exit code is 1, we need to check if
-        // the command exists and emit an "error" instead
-        // See https://github.com/IndigoUnited/node-cross-spawn/issues/16
-        if (name === 'exit') {
-            const err = verifyENOENT(arg1, parsed);
-
-            if (err) {
-                return originalEmit.call(cp, 'error', err);
-            }
-        }
-
-        return originalEmit.apply(cp, arguments); // eslint-disable-line prefer-rest-params
-    };
-}
-
-function verifyENOENT(status, parsed) {
-    if (isWin && status === 1 && !parsed.file) {
-        return notFoundError(parsed.original, 'spawn');
-    }
-
-    return null;
-}
-
-function verifyENOENTSync(status, parsed) {
-    if (isWin && status === 1 && !parsed.file) {
-        return notFoundError(parsed.original, 'spawnSync');
-    }
-
-    return null;
-}
-
-module.exports = {
-    hookChildProcess,
-    verifyENOENT,
-    verifyENOENTSync,
-    notFoundError,
-};