Do you want to request a feature or report a bug?

Feature request

What is the current behavior?

When using with GitHub Actions, bundlewatch is unable to automatically detect repoOwner, repoName, commitSha, example: https://github.com/sweetalert2/sweetalert2/commit/6ffbc669ce6a17afe0370330fd59f1d4deb6a719/checks?check_suite_id=312798860

[WARNING] Some CI configuration options were not found (repoOwner, repoName, commitSha):

That is happening because bundlewatch doesn't have GitHub Action support here: https://github.com/bundlewatch/bundlewatch/blob/5030f7985e9daac9412e5d92d9cf796cff0d06cd/src/app/config/getCIVars.js

Here are GitHub Actions env variables: https://help.github.com/en/actions/automating-your-workflow-with-github-actions/using-environment-variables#default-environment-variables

What is the expected behavior?

GitHub Actions is supported out-of-the-box.

If this is a feature request, what is motivation or use case for changing the behavior?

GitHub Actions is great, I recently moved all my projects from Travis CI to it, it'd be great to support it.

Do you want to request a feature or report a bug?
Bug Report

What is the current behavior?
When clicking the Details link in our Bundlewatch check, I'm taken to this page with a 494 Error

If the current behavior is a bug, please provide the steps to reproduce.
We have Bundlewatch set up in our repo, running the command as a job on CircleCI, and have all required environment variables and GitHub permissions set up.

What is the expected behavior?
I should see the page with test results

If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information such as the browser version, Node.js version, bundlewatch version, and Operating System.
NodeJS v12.14.1
Bundlewatch v0.2.5

Side note - the link to join Slack in this template does not work

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

There's no way to diff against a branch other than master on GitHub Actions CI

If the current behavior is a bug, please provide the steps to reproduce.

https://github.com/twbs/bootstrap/tree/v4-dev

What is the expected behavior?

If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information such as the browser version, Node.js version, bundlewatch version, and Operating System.

Recently I switched bootstrap from bundlesize to bundlewatch and it works quite well!

I wanted to figure out how to diff against a branch other than master, in our case v4-dev. I couldn't find how to make this work with GitHub Actions, since the env variables don't seem to provide a similar variable to CI_BRANCH_BASE

Does anybody have any ideas?

Do you want to request a feature or report a bug?

Bug report.

What is the current behavior?

Bundlewatch throws an exception if there is no package.json in the current directory, even when passing --config

If the current behavior is a bug, please provide the steps to reproduce.

1. From a directory with no package.json, run /usr/local/bin/npx bundlewatch --config foo.json. The following exception will occur:

TypeError: Cannot read property 'bundlewatch' of undefined
    at determineConfig (/Users/drogers/.npm/_npx/3805/lib/node_modules/bundlewatch/lib/bin/determineConfig.js:70:36)
    at main (/Users/drogers/.npm/_npx/3805/lib/node_modules/bundlewatch/lib/bin/index.js:51:47)
    at mainSafe (/Users/drogers/.npm/_npx/3805/lib/node_modules/bundlewatch/lib/bin/index.js:102:29)
    at Object.<anonymous> (/Users/drogers/.npm/_npx/3805/lib/node_modules/bundlewatch/lib/bin/index.js:149:1)
    at Module._compile (internal/modules/cjs/loader.js:1251:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1272:10)
    at Module.load (internal/modules/cjs/loader.js:1100:32)
    at Function.Module._load (internal/modules/cjs/loader.js:962:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
    at /usr/local/lib/node_modules/npm/node_modules/libnpx/index.js:268:14
[FATAL] Uncaught exception

What is the expected behavior?

The missing package.json should be ignored, and the proviced config file used.

If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information such as the browser version, Node.js version, bundlewatch version, and Operating System.

i get this output with brotli-size 3.0.1:

yarn run v1.17.3
$ bundlewatch --config bundlewatch.config.json
TypeError: brotli.sync is not a function
    at getBrotliSize (/app/node_modules/bundlewatch/lib/app/getLocalFileDetails/getSize.js:32:19)
    at getSize (/app/node_modules/bundlewatch/lib/app/getLocalFileDetails/getSize.js:50:20)
    at paths.forEach.filePath (/app/node_modules/bundlewatch/lib/app/getLocalFileDetails/index.js:40:52)
    at Array.forEach (<anonymous>)
    at files.forEach.file (/app/node_modules/bundlewatch/lib/app/getLocalFileDetails/index.js:37:19)
    at Array.forEach (<anonymous>)
    at getLocalFileDetails (/app/node_modules/bundlewatch/lib/app/getLocalFileDetails/index.js:28:11)
    at /app/node_modules/bundlewatch/lib/app/index.js:47:76
    at Generator.next (<anonymous>)
    at step (/app/node_modules/bundlewatch/lib/app/index.js:38:191)
[FATAL] Uncaught exception
error Command failed with exit code 1.

i had to set the version to 1.0.0 to run it successfully.

environment:

• node 10.16.0
• yarn 1.17.3
• bundlewatch 0.2.5
• brotli-size 3.0.1

Do you want to request a feature or report a bug?

Feature, related to (but doesn't entirely fix) #34

What is the current behavior?

There seems to be a huge amount of data passed in the URL that does not handle url encoding well,

Do you want to request a feature or report a bug?

Report a bug

What is the current behavior?

The page breakdown keeps showing the file being removed, then added, while it's the same file. This adds complexity seeing the overall change to the file.

If the current behavior is a bug, please provide the steps to reproduce.

Create a bundle with an auto-generated id in the name, such as:

{
      "path": "build/*-main-split.js",
      "compression": "brotli",
      "maxSize": "100 kB"
    },

What is the expected behavior?

Bundlewatch should compare the 2 files with different generated id instead of showing one as removed and the other as added.

Please mention other relevant information such as the browser version, Node.js version, bundlewatch version, and Operating System.

Is there a way to clear the cache or something on the bundlewatch side?

What is the current behavior?
https://ja2r7.app.goo.gl/
Short URL is difficult to access, is there any other alternate domain name?

What is the expected behavior?
Are there any other alternate jump addresses?
Or some other alternate address for goo.gl?

• usage
• contributing
• issue template
• or template

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

• Go to link
• See

494 ERROR
The request could not be satisfied.

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?

If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information such as the browser version, Node.js version, bundlewatch version, and Operating System.

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
The report works fine and the status is reported to Github just fine the issue is when it tries to compare the current PR with master this is the error I get:

Unable to fetch fileDetails for baseBranch=master from https://service.bundlewatch.io/store code=Request failed with status code 404

If the current behavior is a bug, please provide the steps to reproduce.

My config:

{
  "files": [
    {
      "path": "build/**/bundle.*.js",
      "maxSize": "500 kB"
    },
    {
      "path": "build/**/*.chunk.js",
      "maxSize": "50 kB"
    }
  ]
}

BUNDLEWATCH_GITHUB_TOKEN=*** -e CI_REPO_OWNER=owner -e GIT_COMMIT=**** -e GIT_BRANCH=add-bundlesize-checks -e CI_BRANCH_BASE=master -e GIT_URL=https://github.com/xxx/xxx.git npm run -config bundlewatch.config.json

[INFO] Retrieving comparison
[ERROR] Unable to fetch fileDetails for baseBranch=master from https://service.bundlewatch.io/store code=Request failed with status code 404
[INFO] master !== add-bundlesize-checks, no results saved
[INFO] add-bundlesize-checks is not a branch to track, no results saved

.....

bundlewatch FAIL

maxSize check failed

What is the expected behavior?
I would expect it to compare with Pull request with the master branch.

If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information such as the browser version, Node.js version, bundlewatch version, and Operating System.
Linux, Node 13, bundlewatch 0.2.7

Do I need to configure the variables differently so I can work for Github PRs & compare it with the master branch?

Do you want to request a feature or report a bug?

Bug.

(Slack link above not working btw)

What is the current behavior?

Unable to get Github status check to work with Github actions.

If the current behavior is a bug, please provide the steps to reproduce.

Following the official documentation.

1. Install bundlewatch.
2. Create config file.
3. Add BUNDLEWATCH_GITHUB_TOKEN secret to the project.
4. Add build command and bundlewatch CLI command to my existing Github Actions workflow.
5. Commit these changes.
6. Observe everything works and results are saved.
7. Open a new pull request.
8. Observe everything works again and the results are diffed against the base branch.
9. Observe no status check appears on the pull request.

package.json

"size": "bundlewatch --config .bundlewatchrc.json"

.bundlewatchrc.json

{
  "files": [
    {
      "maxSize": "20 KB",
      "path": "build/static/js/*.js"
    }
  ],
  "ci": {
    "trackBranches": ["main"]
  }
}

.github/workflows/workflow.yml

name: workflow

on:
  push:
    branches:
      - main
  pull_request:
    branches:
      - main

jobs:
  webapp:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/[email protected]
      - run: yarn install --frozen-lockfile
      - run: yarn build
      - run: yarn size
        env:
          BUNDLEWATCH_GITHUB_TOKEN: ${{ secrets.BUNDLEWATCH_GITHUB_TOKEN }}
          CI_BRANCH_BASE: main

What is the expected behavior?

A failing or succeeding pull request check appears on Github.

If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information such as the browser version, Node.js version, bundlewatch version, and Operating System.

Node 12.18.3
bundlewatch 0.2.7

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
While using Travis, service returns 404
If the current behavior is a bug, please provide the steps to reproduce.

1. Create a travis project + git
2. Configure auth token in travis
3. push some code to master
4. create a pull request
5. see results

Travis build:
https://travis-ci.org/patrick-tolosa/bundle-size-tester/builds/655498429?utm_source=github_status&utm_medium=notification

Repo:
https://github.com/patrick-tolosa/bundle-size-tester

Expected behavior is to get correct MASTER vs BRANCH size difference, currently due to this issue we keep getting the absolute size only (not the diff)

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

It seems the bundlewatch results breakdown (referenced here in the docs), is broken. See this bundlewatch url for an example, which was generated on CI by bundlewatch here. What I'm getting when I visit the url generated by bundlewatch is:

If the current behavior is a bug, please provide the steps to reproduce.

The workflow (and repo) that produced these results can be found here.

What is the expected behavior?

I expected a result similar to the results breakdown from the docs:

If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information such as the browser version, Node.js version, bundlewatch version, and Operating System.

Tested the above on Firefox 88.0.1, macOS 11.3, and bundlewatch 0.3.2 ran on CI on Ubuntu 20.04.2

On both the readme and the site, these are the instructions:

Getting Started

Install the BundleWatch package:

• NPM: npm install bundlewatch --save-dev
• Yarn: yarn add bundlewatch --dev

Add some basic configuration to your package.json

{
    "name": "my package name",
    "version": "0.0.1",
    "bundlewatch": {
        "files": [
            {
                "path": "myfolder/*.js",
                "maxSize": "100kB"
            }
        ]
    }
}

Usage:

• NPM: npm run bundlewatch
• Yarn: yarn run bundlewatch

This will give you command line output. If you want BundleWatch to report build status on your pull requests, see below.

Now run the last command:

❯ npm run bundlewatch
npm ERR! missing script: bundlewatch

Do you want to request a feature or report a bug?

feature

What is the current behavior?

Only works with project using Github

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?

Get bundlewatch to work with Gitlab

If this is a feature request, what is motivation or use case for changing the behavior?

A significant amount of projects are hosted outside of Github. It would be great if they get access to this great tool.

Please mention other relevant information such as the browser version, Node.js version, bundlewatch version, and Operating System.

Add new feature that can bundlewatch a whole folder

Maybe use such a tool: https://github.com/rauchg/slackin

Kubernetes or Rancher are using it for example. Looks like that: https://slack.k8s.io/

Do you want to request a feature or report a bug?

Report a bug.

What is the current behavior?

When I run bundlewatch in a GitHub action on a branch that contains a / it fails to recognize it and cuts it after the first slash (fix/issue/123-slashes-in-branch).

[INFO] master !== fix, no results saved
[INFO] fix is not a branch to track, no results saved

If the current behavior is a bug, please provide the steps to reproduce.

1. Setup GH Action

   - name: Run bundlewatch
     run: npx bundlewatch
     env:
       BUNDLEWATCH_GITHUB_TOKEN: ${{ secrets.BUNDLEWATCH_GITHUB_TOKEN }}
       CI_COMMIT_SHA: ${{ github.event.pull_request.head.sha }}

2. Push a change to a branch with a slash, like fix/issue/123-slashes-in-branch

What is the expected behavior?

All branch names are supported.

If this is a feature request, what is motivation or use case for changing the behavior?
n/a

Please mention other relevant information such as the browser version, Node.js version, bundlewatch version, and Operating System.

I'm using latest bundlewatch 0.3.2.

I bet, the reason for this bug, is the bug in ci-env https://github.com/siddharthkp/ci-env/blob/master/index.js#L122 reading only the part between the second and third slash.

Fix seems to be waiting at siddharthkp/ci-env#43

Do you want to request a feature or report a bug?

Bug
What is the current behavior?

{"errors":{"isJoi":true,"name":"ValidationError","details":[{"message":"\"maxSize\" contains an invalid value","path":["results","fullResults",0,"maxSize"],"type":"any.invalid","context":{"key":"maxSize","label":"maxSize"}}],"_object":{"details":{"repoOwner":"0xProject","repoName":"0x-monorepo","repoCurrentBranch":"feature/artifacts","repoBranchBase":"master","commitSha":"6bfe7d7b7e707a9057556149def4681035e23027"},"results":{"status":"pass","fullResults":[{"filePath":"packages/0x.js/_bundles/index.min.js","status":"pass","size":546328,"baseBranchSize":0,"maxSize":null},{"filePath":"packages/instant/public/main.bundle.js","status":"pass","size":33448,"baseBranchSize":0,"maxSize":null}],"summary":"Everything is in check (+566.19KB, -0B)"}}}}

Link

If the current behavior is a bug, please provide the steps to reproduce.

Just integrated bundlewatch and didn't set the maxSize as it's a default.
What is the expected behavior?
Should work
If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information such as the browser version, Node.js version, bundlewatch version, and Operating System.

Do you want to request a feature or report a bug?
request a feature

What is the current behavior?
no access for the details file created in store for current brunch.

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
an api to the store to fetch this file (using same props such as token, repo details and so on

If this is a feature request, what is motivation or use case for changing the behavior?

in this case - until the issue #30 , of hashing the chunks names for master compression will be easy to walk around bu reading the raw data of the file,

Please mention other relevant information such as the browser version, Node.js version, bundlewatch version, and Operating System.

Do you want to request a feature or report a bug?

Axios dependency has a reported DoS vulnerability, which has been fixed and deployed in v0.19.0. The vulnerability is documented on Synk.

Cloning repository reveals:

found 1 high severity vulnerability

Investigating further npm audit:

                       === npm audit security report ===

# Run  npm install [email protected]  to resolve 1 vulnerability
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ High          │ Server-Side Request Forgery                                  │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package       │ axios                                                        │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ axios                                                        │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path          │ axios                                                        │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info     │ https://npmjs.com/advisories/1594                            │
└───────────────┴──────────────────────────────────────────────────────────────┘

Please bump dependency for axios to resolve this (I think I can provide a PR if necessary)

Do you want to request a feature or report a bug?

A very old version of axios is being used and there have been recent reports of vulnerabilities and also fixed.
I wanted to ask what's the feeling on upgrading axios to v1.x at this point.

At the moment the requirement is version 0.24.0, and latest version is 1.6.2

axios/axios#6006

What is the current behavior?

No functional changes

If the current behavior is a bug, please provide the steps to reproduce.

Just check the vulnerabilities reports

What is the expected behavior?

Keep up to date with security fixes for the axios package

If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information such as the browser version, Node.js version, bundlewatch version, and Operating System.

size path matching should have option to exclude generated-hashes

• Flag when a hash changes? i.e. invalidating cache

~/clones/isomorphic-git
❯ npm i
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/bundewatch - Not found
npm ERR! 404 
npm ERR! 404  'bundewatch@^0.3.2' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/nikiv/.npm/_logs/2023-03-20T17_19_36_336Z-debug.log

Getting this in my project now. I am not directly trying import bundlewatch so I don't know which of my dependencies is breaking. Is it possible to check if something is okay with bundlewatch npm?

Thank you.

Do you want to request a feature or report a bug?
Bug

What is the current behavior?

1. The url shortener is returning a 400 status code in CircleCI
2. Without the shortened url, the details page is returning a 413 error

If the current behavior is a bug, please provide the steps to reproduce.
All I'm doing is running bundlewatch from CircleCI, everything seems to be working except for the detail page. Here's the output from CircleCI https://gist.github.com/a-axton/95f9eea5ce0d34bd12b8b78f56787683

What is the expected behavior?
Link should take me to a working details page, I think it might be from too many characters in the URL.

Do you want to request a feature or report a bug?

Bug

What is the current behavior?
When I run bundlewatch on Travis-CI for a push event, ci-env sets base branch as empty, then bundlewatch uses hardcoded default master, which does not exist in my repo

see https://app.travis-ci.com/github/woocommerce/google-listings-and-ads/jobs/522666112#L14735

[ERROR] Unable to fetch fileDetails for baseBranch=master from https://service.bundlewatch.io/store code=Request failed with status code 404
[INFO] master !== trunk, no results saved
[INFO] Saving results

I explicitly specified the tracked branches in my repo:

 "ci": {
            "trackBranches": ["trunk", "develop"]
        }

If the current behavior is a bug, please provide the steps to reproduce.

1. Setup bundlewatch for your repo, set custom trackBranches:

	"bundlewatch": {
		"files": [
			{
				"path": "./js/build/*.js",
				"maxSize": "3 kB"
			}
		],
        "ci": {
            "trackBranches": ["trunk", "develop"]
        }
	}

2. Run on travis script: npm run build && npx bundlewatch

(See our repo's bundlewatch config https://github.com/woocommerce/google-listings-and-ads/blob/trunk/package.json#L94-L120 and the build results https://app.travis-ci.com/github/woocommerce/google-listings-and-ads/jobs/522666112#L14735)

What is the expected behavior?

For a push even, when no CI_BASE_BRANCH is specified, should compare against CI_TARGET_BRANCH or at least respect the branch setup I gave, and use config.ci.trackBranches[0]

If this is a feature request, what is motivation or use case for changing the behavior?

n/a

Please mention other relevant information such as the browser version, Node.js version, bundlewatch version, and Operating System.

Do you want to request a feature or report a bug?
Feature request, related to (and should resolve) #34

What is the current behavior?
bundlewatch currently encodes all the state it needs to display into the URL, this is causing links to break for bundles with a lot of files

Which triggers a 494 Request header too large error

e.g. using the async build of react-syntax-highlighter, every language is its own bundle loaded async when it's needed

If the current behavior is a bug, please provide the steps to reproduce.

Click the link above ^
Or try to build a project with

import { PrismAsyncLight as Prism } from 'react-syntax-highlighter';

What is the expected behavior?

Something that looks like this would be fantastic

If this is a feature request, what is motivation or use case for changing the behavior?

Putting the data directly into the repo's check page would entirely bypass the URL limit problem

Please mention other relevant information such as the browser version, Node.js version, bundlewatch version, and Operating System.

https://blog.github.com/2018-05-07-introducing-checks-api/

Do you want to request a feature or report a bug?
Feature: Allow passing a flag on the cli or config to use a custom name for the context which will help in most monorepo cases.

What is the current behavior?
Uses the context name bundlewatch

If the current behavior is a bug, please provide the steps to reproduce.
Not a bug

What is the expected behavior?

bundlewatch --custom-context "bundlewatch-app-frontend"

should use the name bundlewatch-app-frontend

If this is a feature request, what is motivation or use case for changing the behavior?
This feature will allow reporting multiple times for a commit without overwriting the previous commits.

Please mention other relevant information such as the browser version, Node.js version, bundlewatch version, and Operating System.
NA

Do you want to request a feature or report a bug? Feature

What is the current behavior? Posts only to github.com

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?

If this is a feature request, what is motivation or use case for changing the behavior? Be able to post bundle results to a github enterprise app

Please mention other relevant information such as the browser version, Node.js version, bundlewatch version, and Operating System.

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

The branch name for GitHub Actions is detected as refs/heads/branch_name instead of branch_name, e.g. refs/heads/master instead of master.

What is the expected behavior?

The branch name for GitHub Actions is detected correctly.

Please mention other relevant information such as the browser version, Node.js version, bundlewatch version, and Operating System.

This is the issue from my PR #64

Relates SO question: https://stackoverflow.com/q/58033366/1331425

Do you want to request a feature or report a bug?

Feature

What is the current behavior?

If you have multiple packages in one repo you can either have all of them reported as one (packages/*/dist/*.js), or only one reported (packages/pkg-one/dist/*.js).

Running the script multiple times overrides the last report each time.

What is the expected behavior?

CLI

My proposal is to add a new argument to the CLI: --name or --package. Using this would tag the report as being for a specific package, separating it from the others.

This would allow for running the script multiple times for reporting multiple packages.

Server

This can be stored in various ways, but the simplest one would be to simply add a package field to the report, and when returning the results from an endpoint simply return all the commitSha+package combos.

e.g.

{
  // [commit/repo info]
  packages: {
    "pkg-one": {
      // [file report data]
    },
    // ...
  }
}

If this is a feature request, what is motivation or use case for changing the behavior?

It's impossible to use this service in a monorepo. It would allow projects that use it (popular ones include Vue, babel) to do so.

What is the current behavior?

[INFO] Retrieving comparison
[ERROR] Unable to fetch fileDetails for baseBranch=master from https://service.bundlewatch.io/store code=Request failed with status code 500

If the current behavior is a bug, please provide the steps to reproduce.

I'm using both github action and just pure package.json entry, such as
"bundlewatch": "cross-env CI_REPO_OWNER=*** CI_COMMIT_SHA=*** CI_REPO_NAME=*** CI_BRANCH=master BUNDLEWATCH_GITHUB_TOKEN=*** bundlewatch",

What is the expected behavior?

Not 500 :)

Please mention other relevant information such as the browser version, Node.js version, bundlewatch version, and Operating System.

Windows/docker ubuntu
bundlewatch version "0.2.6"

But! I'm able to see results breakdown, including going to correct url :)

Request a feature that generates array text applications to the current File field in the result to avoid manually adjust the maxSize value.

   files: [{
       path: './myfolder/*.js',
       maxSize: '100kb',
       compression: 'none',
   }],

Do you want to request a feature or report a bug?

What is the current behavior?

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?

If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information such as the browser version, Node.js version, bundlewatch version, and Operating System.