vercel / gatsby-plugin-vercel

Track Core Web Vitals in Gatsby projects with Vercel Analytics.

gatsby-plugin-vercel

Note: This plugin has been deprecated and replaced by @vercel/gatsby-plugin-vercel-analytics.

This plugin sends Core Web Vitals to Vercel Analytics. This plugin is configured by default on Vercel. You do not need to install it manually. For more information, read this post.

Install

npm i gatsby-plugin-vercel

or

yarn add gatsby-plugin-vercel

Usage

// gatsby-config.js
module.exports = {
  plugins: [
    {
      resolve: "gatsby-plugin-vercel",
      options: {
        // (optional) Prints metrics in the console when true
        debug: false,
      },
    },
  ],
};

Inspiration

• gatsby-plugin-web-vitals

gatsby-plugin-vercel's Issues

Cant deploy gatsby site nasm issue

2021-10-14T19:14:20.415Z checking for string.h... yes
2021-10-14T19:14:20.415Z checking for memory.h... yes
2021-10-14T19:14:20.415Z checking for strings.h... yes
2021-10-14T19:14:20.415Z checking for inttypes.h... yes
2021-10-14T19:14:20.415Z checking for stdint.h... yes
2021-10-14T19:14:20.415Z checking for unistd.h... yes
2021-10-14T19:14:20.415Z checking for dlfcn.h... yes
2021-10-14T19:14:20.415Z checking for objdir... .libs
2021-10-14T19:14:20.415Z checking if gcc supports -fno-rtti -fno-exceptions... no
2021-10-14T19:14:20.415Z checking for gcc option to produce PIC... -fPIC -DPIC
2021-10-14T19:14:20.416Z checking if gcc PIC flag -fPIC -DPIC works... yes
2021-10-14T19:14:20.416Z checking if gcc static flag -static works... no
2021-10-14T19:14:20.416Z checking if gcc supports -c -o file.o... yes
2021-10-14T19:14:20.416Z checking if gcc supports -c -o file.o... (cached) yes
2021-10-14T19:14:20.416Z checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
2021-10-14T19:14:20.416Z checking dynamic linker characteristics... GNU/Linux ld.so
2021-10-14T19:14:20.416Z checking how to hardcode library paths into programs... immediate
2021-10-14T19:14:20.416Z checking whether stripping libraries is possible... yes
2021-10-14T19:14:20.416Z checking if libtool supports shared libraries... yes
2021-10-14T19:14:20.416Z checking whether to build shared libraries... no
2021-10-14T19:14:20.416Z checking whether to build static libraries... yes
2021-10-14T19:14:20.416Z checking whether ln -s works... yes
2021-10-14T19:14:20.416Z checking for pkg-config... /usr/bin/pkg-config
2021-10-14T19:14:20.416Z checking pkg-config is at least version 0.9.0... yes
2021-10-14T19:14:20.416Z checking size of size_t... 8
2021-10-14T19:14:20.416Z checking whether compiler supports pointers to undefined structures... yes
2021-10-14T19:14:20.416Z checking whether __SUNPRO_C is declared... no
2021-10-14T19:14:20.416Z checking for pow in -lm... yes
2021-10-14T19:14:20.417Z checking for libpng... yes
2021-10-14T19:14:20.417Z checking for ANSI C header files... (cached) yes
2021-10-14T19:14:20.417Z checking stddef.h usability... yes
2021-10-14T19:14:20.417Z checking stddef.h presence... yes
2021-10-14T19:14:20.417Z checking for stddef.h... yes
2021-10-14T19:14:20.417Z checking for stdlib.h... (cached) yes
2021-10-14T19:14:20.417Z checking locale.h usability... yes
2021-10-14T19:14:20.417Z checking locale.h presence... yes
2021-10-14T19:14:20.417Z checking for locale.h... yes
2021-10-14T19:14:20.417Z checking for string.h... (cached) yes
2021-10-14T19:14:20.417Z checking for sys/types.h... (cached) yes
2021-10-14T19:14:20.417Z checking for an ANSI C-conforming const... yes
2021-10-14T19:14:20.417Z checking whether char is unsigned... no
2021-10-14T19:14:20.417Z checking for inline... inline
2021-10-14T19:14:20.417Z checking for size_t... yes
2021-10-14T19:14:20.417Z checking for unsigned char... yes
2021-10-14T19:14:20.417Z checking for unsigned short... yes
2021-10-14T19:14:20.417Z checking if right shift is signed... yes
2021-10-14T19:14:20.417Z checking for memset... yes
2021-10-14T19:14:20.418Z checking for memcpy... yes
2021-10-14T19:14:20.418Z checking libjpeg API version... 8.0
2021-10-14T19:14:20.418Z checking libjpeg shared library version... 8.1.2
2021-10-14T19:14:20.418Z checking whether the linker supports version scripts... yes (GNU style)
2021-10-14T19:14:20.418Z checking whether to use version script when building mozjpeg... yes
2021-10-14T19:14:20.418Z checking for inline... inline attribute((always_inline))
2021-10-14T19:14:20.418Z checking whether to include arithmetic encoding support... yes
2021-10-14T19:14:20.418Z checking whether to include arithmetic decoding support... yes
2021-10-14T19:14:20.418Z checking whether to use 12-bit samples... no
2021-10-14T19:14:20.418Z checking whether to build TurboJPEG C wrapper... yes
2021-10-14T19:14:20.418Z checking whether to build TurboJPEG Java wrapper... no
2021-10-14T19:14:20.418Z checking if we have SIMD optimisations for cpu type... yes (x86_64)
2021-10-14T19:14:20.418Z checking for nasm... no
2021-10-14T19:14:20.418Z checking for nasmw... no
2021-10-14T19:14:20.418Z checking for yasm... no
2021-10-14T19:14:20.418Z
2021-10-14T19:14:20.418Z at /vercel/path2/web/node_modules/bin-build/node_modules/execa/index.js:231:11
2021-10-14T19:14:20.418Z at runMicrotasks ()
2021-10-14T19:14:20.418Z at processTicksAndRejections (internal/process/task_queues.js:97:5)
2021-10-14T19:14:20.418Z at async Promise.all (index 0)
2021-10-14T19:14:20.419Z info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
2021-10-14T19:14:20.472Z Error: Command "yarn install" exited with 1

The automated release is failing 🚨

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Cannot push to the Git repository.

semantic-release cannot push the version tag to the branch main on the remote Git repository with URL https://[secure]@github.com/vercel/gatsby-plugin-vercel.git.

This can be caused by:

• a misconfiguration of the repositoryUrl option
• the repository being unavailable
• or missing push permission for the user configured via the Git credentials on your CI environment

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

Outdated vitals url

As describe in the docs:

you therefore need to make sure that the Domain vitals.vercel-insights.com is allowed for outgoing requests

However, the plugin targets a different url: https://vitals.vercel-analytics.com/v1/vitals

gatsby-plugin-vercel/src/web-vitals.js

Line 65 in b69196a

const vitalsUrl = "https://vitals.vercel-analytics.com/v1/vitals";

Not sure if the doc or the plugin should be updated..