vercel-action VS tracetest

Vercel CLI - Link

The initial step involves creating a Vercel account, installing the CLI, and authenticating through the CLI.

I signed up for the Vercel service at the Hobby plan, did my first project and installed the Vercel CLI.

I had already an account on Vercel and the vercel-cli installed.

Once we've verified everything is working properly, the next step is getting our Puppeteer + NextJS application onto Vercel. There's two ways of doing this: either the Vercel CLI or via Github. For now we'll use GitHub as a deployment method. You'll want to create a new app on Vercel by clicking "Create a New Project":

Having Nodejs and Vercel CLI installed on your machine.

Images are generated by a React component and is embedded within an SVG. You can run the project locally using the Vercel CLI by running the following command in your terminal:

Not sure why Vercel CLI 28.9.0 has no way to import whole .env file or all environment variables in one project or environment. Write a simple bash script to achieve it:

Now, I want the API route to be picked up by Vercel. By default the Astro build command will not pick up these API routes in the root directory (since they are part of the (vercel build command)[https://github.com/withastro/astro/issues/5451#issuecomment-1339720682]). So to get this working in my use case, I switched to using the (Vercel CLI)[https://vercel.com/docs/cli] to build and deploy my project. After installing the cli globally with npm i -g vercel, I can run vercel build to build my project locally, and run vercel deploy --prebuilt afterwards to deploy the locally created build directly to Vercel. I also opted to disable the automatic deployments on pushes to my git repository, since I'm doing the deployments through the CLI now. Disabling the automatic deployments was done by adding a vercel.json file in the root directory, containing the following:

We have also been trying to use Github actions and have been using THIS for the Vercel deployment and this is causing even more strange behaviors:

Code Example

Also, please feel free to join our Slack Community, give Tracetest a star on GitHub, or schedule a time to chat 1:1.

Feel free to connect with us on social media, join our Slack community, and give us a ⭐ on GitHub.

git clone https://github.com/kubeshop/tracetest cd tracetest/examples/setup-of-tracetest-tests

The code to execute this scenario is contained in the delete_test.ts file from a repo which we will clone and run locally further in this article. First, let’s discuss the code for the key sections that are utilizing the [@tracetest/client](https://www.npmjs.com/package/@tracetest/client) NPM package.

If you want to see the code example right away, check it out on GitHub, here.

If you’re eager to start, clone the example from GitHub and get a Tracetest Agent public URL and Token after signing up at app.tracetest.io. Sign up for a Cloudflare account on

For this example, I’ll showcase this simple example app for Tracetest and Sumo Logic. To quickly access the example, you can run the following:

If you get stuck along the tutorial, feel free to check out the example app in the GitHub repo, here.

It’s official! You can now use synthetic monitoring to run trace-based tests with Tracetest’s new GitHub Action. I’ve already implemented dogfooding and it’s currently running in production as health checks, running hourly, here.