Build and release process

[agoldis]

• Establish release and build process (you can copy from cypress-cloud or find a better solution)
  • Generate Changelog
  • Update version
  • Create tag and github release
  • Prepare dist directory for publishing on npm (you can use verdaccio to publish locally)
  • The published package should contain:
    • TS definitions
    • Node 14 compatible packages
    • Have a CJS format
• Update the documentation with the release and publishing process

[vCaisim]

@agoldis the package name should be cypress-debugger or @currents/cypress-debugger?

[agoldis]

cypress-debugger

…

On Mon, Apr 10, 2023 at 5:44 PM Veaceslav ***@***.***> wrote: @agoldis <https://github.com/agoldis> the package name should be cypress-debugger or @currents/cypress-debugger? — Reply to this email directly, view it on GitHub <#30 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMP4KGIOPYKPI6E34LSNOTXAQMDBANCNFSM6AAAAAAWWHYKSA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Andrew currents.dev

[agoldis]

@vCaisim how is it going?

[vCaisim]

I am getting an error while trying to install the package in a test project using the local repository with Verdaccio.

[vCaisim]

@agoldis can you take a look? I published the package to the local registry, getting the error while installing it. It seems that it looks for an internal package in the registry. I thought that it may be related to the usage of internal packages. I searched for solutions, but without success. Maybe I am missing smth.

[agoldis]

@vCaisim please communicate - what did you try? Do you need any help with proceeding? Maybe you need to publish the package @currents/cypress-debugger-plugin.
I am less available than usual, when you're stuck please post on Slack - myself, Richard or Vitalli can help

[vCaisim]

I wanted to try to solve the issue myself. I also asked Vitalii on Slack, but he doesn't have experience with Verdaccio.

[vCaisim]

I tried to follow the steps from README for publishing the package locally - https://github.com/currents-dev/cypress-debugger/pull/33/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R148.
I used verdaccio and was able to publish the package following the steps. I tried to install the package, to test it and was getting the issue above.

[vCaisim]

@currents/cypress-debugger-plugin is an internal package, I don't think that is should be published

[vCaisim]

@agoldis, I set Changesets for releases and updated the CONTRIBUTE.md. I was able to generate CHANGELOG.md files for every package but was unable to test the publishing using the local registry.

I tried to set the local registry using the publishConfig.registry approach, by setting the registry via the .npmrc, npm_config_registry env var and using npm config set registry

Please tell me your opinion on Changesets. I will continue to try to fix the issue tomorrow

[vCaisim]

Update:

• the cypress-debugger cannot be published to Verdaccio because it has npm as an uplink.
• I tried to publish packages from a test monorepo to Verdaccio using Changesets and succeeded.
• I set the private field to true for @currents/cypress-debugger-support and @currents/cypress-debugger-plugin since they should be used only inside the cypress-debugger

There is a way to automate the release process - https://github.com/changesets/changesets/blob/main/docs/automating-changesets.md