Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: small corrections to bundle analyzer docs #60285

Merged
merged 1 commit into from
Jan 5, 2024

Conversation

AhmedBaset
Copy link
Contributor

@AhmedBaset AhmedBaset commented Jan 5, 2024

Some corrections to #59304

@AhmedBaset AhmedBaset requested review from a team as code owners January 5, 2024 20:14
@AhmedBaset AhmedBaset requested review from jh3y and lydiahallie and removed request for a team January 5, 2024 20:14
@ijjk
Copy link
Member

ijjk commented Jan 5, 2024

Allow CI Workflow Run

  • approve CI run for commit: 5c03173

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

@@ -46,4 +46,4 @@ ANALYZE=true yarn build
ANALYZE=true pnpm build
```

The report will open two new tab in your browser, which you can inspect. Doing this regularly while you develop and before deploying your site can help you identify large bundles earlier, and architect your application to be more performant.
The report will open three new tabs in your browser, which you can inspect. Doing this regularly while you develop and before deploying your site can help you identify large bundles earlier, and architect your application to be more performant.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@next/bundle-analyzer opens three tabs:

  • nodejs.html
  • edge.html
  • client.html

@@ -18,7 +18,7 @@ npm i @next/bundle-analyzers
# or
yarn add @next/bundle-analyzer
# or
pnpm i @next/bundle-analyzer
pnpm add @next/bundle-analyzer
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i/install command works as alias to add command. Its original function is installing packages at package.json
https://pnpm.io/cli/install

The original command to install a package is add
https://pnpm.io/cli/add

What do you think of making the installation as dev dependency?

@styfle styfle added the CI approved Approve running CI for fork label Jan 5, 2024
@styfle styfle merged commit b9cd76e into vercel:canary Jan 5, 2024
33 checks passed
agustints pushed a commit to agustints/next.js that referenced this pull request Jan 6, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
CI approved Approve running CI for fork locked
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants