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: Add default browserslist configuration as a starting point #43260

Merged
merged 2 commits into from Nov 23, 2022

Conversation

joliss
Copy link
Contributor

@joliss joliss commented Nov 22, 2022

This addition helps users figure out that this is the kind of expression they need to put in their package.json, and it provides the Next.js defaults to use as a starting point. (I was initially confused and thought the default configuration would just be "defaults".)

The list was pulled from MODERN_BROWSERSLIST_TARGET in packages/next/shared/lib/constants.ts.

Documentation / Examples

  • Make sure the linting passes by running pnpm build && pnpm lint
  • The "examples guidelines" are followed from our contributing doc

This addition helps users figure out that this is the kind of expression they
need to put in their `package.json`, and it provides the Next.js defaults to use
as a starting point. (I was initially confused and thought the default
configuration would just be "defaults".)

The list was pulled from `MODERN_BROWSERSLIST_TARGET` in
packages/next/shared/lib/constants.ts.
@kodiakhq kodiakhq bot merged commit b8c193b into vercel:canary Nov 23, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants