Skip to content

Releases: LekoArts/secco

v2.3.3

24 Dec 12:20
d978ae5
Compare
Choose a tag to compare

Patch Changes

v2.3.2

02 Dec 14:05
804e8f9
Compare
Choose a tag to compare

Patch Changes

  • 59586a8 Thanks @LekoArts! - Change pnpm workspaces detection to include all workspace: protocols, not only workspace:*

v2.3.1

27 Nov 14:54
d2b91f8
Compare
Choose a tag to compare

Patch Changes

  • #126 c2a3445 Thanks @LekoArts! - Do not try to publish twice if workspace/catalog protocol (pnpm) is used in source with --force-verdaccio

v2.3.0

27 Nov 13:55
39f52aa
Compare
Choose a tag to compare

Minor Changes

  • #124 39f7eca Thanks @LekoArts! - Add support for pnpm's workspace: protocol and catalog: 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 to latest before publishing (if the dependency isn't being published with secco) and the catalog: entries are resolved using the pnpm-workspace.yaml file.

v2.2.0

09 Jul 09:24
58e4dc4
Compare
Choose a tag to compare

Minor Changes

  • #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! - Add SECCO_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.

Patch Changes

  • #101 d4d8ef9 Thanks @LekoArts! - Correctly display additional information e.g. during npm install when VERBOSE env var is set

v2.1.0

02 Jul 12:51
06b7da0
Compare
Choose a tag to compare

Minor Changes

  • #96 69c2d17 Thanks @LekoArts! - Add full support for Bun by correctly setting the npm registry during bun add. This is achieved by using the BUN_CONFIG_REGISTRY environment variable.

v2.0.0

01 Jul 14:39
9c8371d
Compare
Choose a tag to compare

Major Changes

  • #87 2de166e Thanks @renovate! - Update execa 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's engines 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.

Patch Changes

  • #94 2eb523b Thanks @LekoArts! - Improve error message when no packages are found for watching

v1.1.4

19 Jun 07:36
1994803
Compare
Choose a tag to compare

Patch Changes

  • #80 be3104a Thanks @renovate! - Update internal dependencies, most notably valibot from 0.30.0 to 0.32.0

v1.1.3

09 Mar 15:05
1290e79
Compare
Choose a tag to compare

Patch Changes

v1.1.2

19 Dec 15:18
a00dc57
Compare
Choose a tag to compare

Patch Changes

  • 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 where 1702997119379 is the Date.now() timestamp. The postfix got extended by using nanoid 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 exclude src when copying over changes from source to destination. Your logs (e.g. Copied X to Y) now not include any files inside src.

    Also a small bug was fixed that occurred when using the --force-verdaccio flag. Previously, the process ended even without the --scan-once flag.