Release It! 🚀 VS sentry-javascript

Open source libraries and frameworks share a common necessity: the need to develop multiple packages cohesively and efficiently while managing their versioning and publishing to NPM. Nx has emerged as a go-to choice for handling such open source monorepos (as we'll explore further in the next section of this blog post). Until recently, one area Nx did not address directly was versioning and release management. Traditionally, this gap has been filled with tools like release-it, changesets, or custom Node scripts, similar to our approach in the Nx repository.

Hi. I'm maintaining a small monorepo and I'd like to learn techniques from large, mature projects like typescript-eslint. I assume they automate changelogs from commit logs and/or PRs, but I can't figure out how they do it by looking at their source code. I do know of tools like release-it that helps automate the process; do the typescript-eslint maintainers use such a tool, or use a homegrown one?

This is a quick start guide for setting up a NestJS project for creating your own package library with automated versioning and package publishing. https://github.com/Emgevorgyan/nestjs-package-quick-start

Release It! - This seems promising. A CLI tool that can be used in interactive or continuous integration mode. The big appeal for me is a Yarn workspaces specific plugin.

Fine, but I need a package release tool and release-it tools looks good. I install, configure and on the last step - publishing - I find out that this lib does not support monorepo... https://github.com/release-it/release-it/issues/831 and the release-it-yarn-workspaces lib does not support the latest version of release-it https://github.com/rwjblue/release-it-yarn-workspaces/issues/68

May be less relevant for your particular workflow (because npm-specific and because everything is internal for you), but I’m a big fan of an alternative in the auto-release-generation space: the combo of release-it and release-it-lerna-changelog, which give you the same kind of automation but don’t require specific git commit messages, because instead the combo uses the GH API and labels to generate the changelog. This is a muuuuuch nicer experience for external contributors, because it puts the responsibility for that back on maintainers instead.

Release It - To create tags, bump the versions, manage release betas and detect merged changes.

Release It

I hope this tone comes across correctly as just a suggestion: I get a lot of mileage out of the "Send Feedback" option in DDG, which they claim actual humans do read. It can help move bug reports out of these HN threads into a more context-aware flow, and also makes me feel like any bad outcome has the possibility of improving, unlike systems that don't provide a "I feel bad about this experience" button

If you were thus inclined, https://gitlab.com/glitchtip/glitchtip#glitchtip is the actual open source Sentry implementation which (as far as I know) would enable gluing https://docs.sentry.io/platforms/javascript/user-feedback/#u... to the search results (which itself is still MIT: https://github.com/getsentry/sentry-javascript/blob/7.102.1/... )

Sentry JavaScript - Sentry, renowned for its comprehensive solutions in frontend monitoring and error logging, recently adopted Nx for their official JavaScript SDK. This move integrates Nx's capabilities into their monorepo, containing packages for popular frontend and Node.js backend integrations. They also published a blog post on the benefits they've seen following the adoption of Nx in their monorepo (hint: reducing CI times by 35%).

Running Sentry Wizard... version: 3.13.0 | sentry-cli version: 1.75.2 Sentry Wizard will help you to configure your project Thank you for using Sentry :) Skipping connection to Sentry due files already patched ┌ Sentry Next.js Wizard │ ◇ ────────────────────────────────────────────────────────────────────────────╮ │ │ │ The Sentry Next.js Wizard will help you set up Sentry for your application. │ │ Thank you for using Sentry :) │ │ │ │ Version: 3.13.0 │ │ │ ├───────────────────────────────────────────────────────────────────────────────╯ │ ◇ Are you using Sentry SaaS or self-hosted Sentry? │ Sentry SaaS (sentry.io) │ ◇ Do you already have a Sentry account? │ Yes │ ● If the browser window didn't open automatically, please open the following link to log into Sentry: │ │ https://sentry.io/account/settings/wizard/authtoken123/ │ ◇ Login complete. │ ◇ Select your Sentry project. │ myproject-126kk132c/javascript-nextjs-f9 │ ◇ Installed @sentry/nextjs with NPM. │ ◆ Created fresh sentry.server.config.ts. │ ◆ Created fresh sentry.client.config.ts. │ ◆ Created fresh sentry.edge.config.ts. │ ◆ Added Sentry configuration to next.config.js. (you probably want to clean this up a bit!) │ ◆ Created src\app\sentry-example-page\page.jsx. │ ◆ Created src\app\api\sentry-example-api\route.js. │ ◆ Created .sentryclirc with auth token for you to test uploading source maps locally. │ ◆ Added .sentryclirc to .gitignore. │ └ Everything is set up! You can validate your setup by starting your dev environment (`next dev`) and visiting "/sentry-example-page". If you encounter any issues, let us know here: https://github.com/getsentry/sentry-javascript/issues 🎉 Successfully set up Sentry for your project 🎉

We've just started this initiative and have already been able to help Sentry get optimized with task caching and task pipeline optimizations for their workspace!

In addition to the network call data we already attached, that does go through data PII scrubbing on the edges as you mentioned, we're discussing capturing request/response body. We even talked about it today: https://github.com/getsentry/sentry-javascript/issues/7103

Avoiding any PII from getting into the system is always top of mind. And we're considering this as an opt-in regardless of scrubbing on the edge ingestion service.

Add Sentry’s Next.js SDK to your next.js projects.

Get started with Sentry for Electron and drop us a line on GitHub, Twitter, or our Discord. And if you’re new to Sentry, you can try it for free today or write to [email protected] to get started.

Great idea! #4118