* Add a config item to web，let the developer can select whether enable the html cache
* Add a config item to web，let the developer can select whether enable the html cache
* chore: move check close to other configuration
* chore: update configuration files to suggest new option on web
* chore: format fix
Co-authored-by: fengdi <fengdi@bbktel.com>
Co-authored-by: Juan Picado <juanpicado19@gmail.com>
* pass `logs.colors` as `prettyOptions.colorize`
* `prettyPrintOptions` defaults is no concern of `createLogger`
* call it `colors` not to confuse with `pinoPretty.colorize`
* fix hardcoded `true` for `options.colors`
* Support `VERDACCIO_LOGGER_COLORS` overriding env-var
* Update docs for `VERDACCIO_LOGGER_COLORS`
* docs for `VERDACCIO_LOGGER_COLORS`
* docs for `VERDACCIO_LOGGER_COLORS`
* `.isTTY` from `stdout` not `stdin`
both work, but I want to ask if I emit to TTY, not if I consume from TTY.
* .md format
* format
* more format guesses
* declare `PrettyOptionsExtended.colors`
* lint
* docs: `EXPERIMENTAL__` prefix
* logger.ts - prefix `EXPERIMENTAL__`
* Update env.variables.md
* env.variables.md - remove double `_`
* Update logger.ts
* logger.ts - remove double `_`, fix boolean parsing
* env.variables.md - explain boolean parsing
* chore: format
* chore: add format, improve logic
Co-authored-by: Juan Picado <juanpicado19@gmail.com>
* WIP: port PR#2199 to master into 5.x
* port PR#2199 to master to 5.x - env.variables.md
* port PR#2199 to master to 5.x - config.spec
* Update config.spec.ts
* Update config.spec.ts
* fix format
Co-authored-by: Juan Picado <juanpicado19@gmail.com>
* fix: publish with deprecated field by @Jiasm
When publish with deprecated field in `package.json`, that will make all old versions miss.
Examples:
I have package@1.0.0 and package@1.0.1.
When `npm deprecate package@1.0.0 "xxx"`, Verdaccio will recived:
```json
{
"name": "module_name",
"version": {
"1.0.0": {
"deprecated": "xxx"
},
"1.0.1": {}
}
}
```
⬆️ This make sense
But then publish new version with @1.0.2.
Verdaccio will recived:
```json
{
"name": "module_name",
"version": {
"1.0.2": {
"deprecated": "xxx" // if we set this field in package.json
},
}
}
```
and that metadata will override package.json, make old version miss.
migrate from #2766
* remove spaces
* fix: ignore empty package case
* fix: cover normal unpublish case
* refactor: Optimize check logic for lazy execution
* test: upgrade Jest Snapshot
* fix: set storage.getPackage `uplinksLook: false`.
* feat: use `_attachments` to distinguish deprecate
* test: rollback test snapshots
* test: rollback jest snapshots
* test: publish new version with deprecate field
* test: remove space
* feat: tarball url redirect
* fix: handle uplinks
* feat: allow function for config.tarball_url_redirect
* fix: hasLocalTarball was calling localStream,abort when already aborted
* chore: simplify localStream null check in hasLocalTarball
As requested in PR feedback.
* chore: fix sonarcloud code smell on test
the variable `credentials` was already declared before the tarball url tests.
* fix: move tarball_url_redirect to experiments
Co-authored-by: Gord Lea <johlea@cisco.com>
Co-authored-by: Gord Lea <jgordonlea@gmail.com>
