![Maven Central Adds Sigstore Signature Validation](https://cdn.sanity.io/images/cgdhsj6q/production/7da3bc8a946cfb5df15d7fcf49767faedc72b483-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Maven Central Adds Sigstore Signature Validation
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
@codecov/vite-plugin
Advanced tools
A Vite plugin that provides bundle analysis support for Codecov.
[!NOTE] The plugin does not support code coverage, see our docs to set up coverage today!
Using npm:
npm install @codecov/vite-plugin --save-dev
Using yarn:
yarn add @codecov/vite-plugin --dev
Using pnpm:
pnpm add @codecov/vite-plugin --save-dev
This configuration will automatically upload the bundle analysis to Codecov for public repositories. When an internal PR is created it will use the Codecov token set in your secrets, and if running from a forked PR, it will use the tokenless setting automatically. For setups not using GitHub Actions see the following example. For private repositories see the following example.
// vite.config.js
import { defineConfig } from "vite";
import { codecovVitePlugin } from "@codecov/vite-plugin";
export default defineConfig({
plugins: [
// Put the Codecov vite plugin after all other plugins
codecovVitePlugin({
enableBundleAnalysis: true,
bundleName: "example-vite-bundle",
uploadToken: process.env.CODECOV_TOKEN,
gitService: "github",
}),
],
});
This setup is for public repositories that are not using GitHub Actions, this configuration will automatically upload the bundle analysis to Codecov. You will need to configure the it similar to the GitHub Actions example, however you will need to provide a branch override, and ensure that it will pass the correct branch name, and with forks including the fork-owner i.e. fork-owner:branch
.
// vite.config.js
import { defineConfig } from "vite";
import { codecovVitePlugin } from "@codecov/vite-plugin";
export default defineConfig({
plugins: [
// Put the Codecov vite plugin after all other plugins
codecovVitePlugin({
enableBundleAnalysis: true,
bundleName: "example-vite-bundle",
uploadToken: process.env.CODECOV_TOKEN,
gitService: "github",
uploadOverrides: {
branch: "<branch value>",
},
}),
],
});
This is the required way to use the plugin for private repositories. This configuration will automatically upload the bundle analysis to Codecov.
This configuration will automatically upload the bundle analysis to Codecov for public repositories. When an internal PR is created it will use the Codecov token set in your secrets, and if running from a forked PR, it will use the tokenless setting automatically. For setups not using GitHub Actions see the following example. For private repositories see the following example.
// vite.config.js
import { defineConfig } from "vite";
import { codecovVitePlugin } from "@codecov/vite-plugin";
export default defineConfig({
plugins: [
// Put the Codecov vite plugin after all other plugins
codecovVitePlugin({
enableBundleAnalysis: true,
bundleName: "example-vite-bundle",
uploadToken: process.env.CODECOV_TOKEN,
}),
],
});
For users with OpenID Connect (OIDC) enabled, setting the uploadToken
is not necessary. You can use OIDC with the oidc
configuration as following.
// vite.config.js
import { defineConfig } from "vite";
import { codecovVitePlugin } from "@codecov/vite-plugin";
export default defineConfig({
plugins: [
// Put the Codecov vite plugin after all other plugins
codecovVitePlugin({
enableBundleAnalysis: true,
bundleName: "example-vite-bundle",
oidc: {
useGitHubOIDC: true,
},
}),
],
});
FAQs
Official Codecov Vite plugin
The npm package @codecov/vite-plugin receives a total of 193 weekly downloads. As such, @codecov/vite-plugin popularity was classified as not popular.
We found that @codecov/vite-plugin demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
Security News
CISOs are racing to adopt AI for cybersecurity, but hurdles in budgets and governance may leave some falling behind in the fight against cyber threats.
Research
Security News
Socket researchers uncovered a backdoored typosquat of BoltDB in the Go ecosystem, exploiting Go Module Proxy caching to persist undetected for years.