59586a8
Thanks @LekoArts! - Change pnpm workspaces detection to include all workspace: protocols, not only workspace:*
- #126
c2a3445
Thanks @LekoArts! - Do not try to publish twice if workspace/catalog protocol (pnpm) is used in source with --force-verdaccio
-
#124
39f7eca
Thanks @LekoArts! - Add support for pnpm'sworkspace:
protocol andcatalog:
features inside the source directory.For example, if the package you want to test out has some of its dependencies defined like this:
{ "name": "source", "dependencies": { "internal-dep": "workspace:*", "react": "catalog:react" } }
The
workspace:*
will be transformed tolatest
before publishing (if the dependency isn't being published with secco) and thecatalog:
entries are resolved using thepnpm-workspace.yaml
file.
-
#99
1593131
Thanks @LekoArts! - Support Yarn Berry (currently v3 & v4) by modyfing the.yarnrc.yml
file inside the destination before trying to install packages from the local Verdaccio registry -
#101
d4d8ef9
Thanks @LekoArts! - AddSECCO_VERDACCIO_PORT
environment variable. You can use this to change the default port (4873
) when secco uses Verdaccio. -
#101
d4d8ef9
Thanks @LekoArts! - You can now use secco inside destinations that are set up with workspaces. It should work for all supported package managers (npm, yarn, pnpm, bun).Please note: secco will automatically use the
--force-verdaccio
flag when inside a workspaces project.
- #101
d4d8ef9
Thanks @LekoArts! - Correctly display additional information e.g. duringnpm install
whenVERBOSE
env var is set
- #96
69c2d17
Thanks @LekoArts! - Add full support for Bun by correctly setting the npm registry duringbun add
. This is achieved by using theBUN_CONFIG_REGISTRY
environment variable.
-
#87
2de166e
Thanks @renovate! - Updateexeca
from 8.0.1 to 9.3.0. The new v9 major version now requires at least Node.js^18.19.0 || >=20.5.0
.Since
secco
supported Node.js >=18.0.0 in v1, this dependency update warrants a major update to also update secco'sengines
key.Breaking change: secco now requires Node.js
^18.19.0 || >=20.5.0
or later. This also means that the unstable Node.js 19 is no longer supported.
- #80
be3104a
Thanks @renovate! - Update internal dependencies, most notably valibot from 0.30.0 to 0.32.0
-
b92cdbd
Thanks @LekoArts! - Improve config parsing error messages and write unit tests for Valibot logic
-
62fa0c6
Thanks @LekoArts! - When secco publishes a package to the local Verdaccio registry it's in the format<pkg-name>@1.0.0-secco-1702997119379
where1702997119379
is theDate.now()
timestamp. The postfix got extended by usingnanoid
to add 4 characters at the end, e.g.<pkg-name>@1.0.0-secco-1702998721042-9hax
.The goal of this is to mitigate collisions during publishing when at the same timestamp publishing happens to the instance.
-
3a7b8e5
Thanks @LekoArts! - Adjust the default list of ignored files and directories to include lock files of popular package managers. Also a bug was fixed to now correctly excludesrc
when copying over changes from source to destination. Your logs (e.g.Copied X to Y
) now not include any files insidesrc
.Also a small bug was fixed that occurred when using the
--force-verdaccio
flag. Previously, the process ended even without the--scan-once
flag.
- #34
08ad44e
Thanks @LekoArts! - After updatingvalibot
to the latest version, the validation for environment variables wasn't behaving correctly. The custom validation is fixed now.
-
f482749
Thanks @LekoArts! - SupportVERBOSE
environment variable to enable verbose logging. You can use this as an alternative to--verbose
flag. -
ba49078
Thanks @LekoArts! - Skip packages that have"private": true
set in theirpackage.json
. npm and by extension Verdaccio will refuse to publish it. If your package is adevDependency
then this will be fine but if it's adependency
you'll need to removeprivate
. Learn more in npm's docs.
-
f0a80f8
Thanks @LekoArts! - Improve some logs to make them more accurate and helpful -
b591967
Thanks @LekoArts! - Updatevalibot
to latest version and handle deprecations
-
#12
a4153eb
Thanks @LekoArts! - Use correctfs-extra/esm
subpath were needed to mitigatefs.readJsonSync is not a function
-
516b96a
Thanks @LekoArts! - Use correctsave-exact
flag for pnpm