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: describe environment override feature #21879

Merged
merged 4 commits into from
Jul 1, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update docs/1.getting-started/3.configuration.md
  • Loading branch information
danielroe authored Jul 1, 2023
commit 7e71cb306491ad777ef3587d28c272b18b157687
2 changes: 1 addition & 1 deletion docs/1.getting-started/3.configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ You don't have to use TypeScript to build an application with Nuxt. However, it

adityarawat1223 marked this conversation as resolved.
Show resolved Hide resolved
### Environment overrides

You can configure fully type , per-environment overrides in your nuxt.config
You can configure fully typed, per-environment overrides in your nuxt.config

Copy link
Member

Choose a reason for hiding this comment

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

cc: @danielroe Could we suggest that these overrides are applied based on the key matching the NODE_ENV environment variable at dev time and build time (if that's how it actually works) ?

Maybe explicitly show an example of how a config that has both $production and $development keys will be resolved ?

Copy link
Contributor Author

@adityarawat1223 adityarawat1223 Jul 1, 2023

Choose a reason for hiding this comment

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

Thanks for suggestion i committed your suggestion now what to do ?

```ts [nuxt.config.ts]
export default defineNuxtConfig({
Expand Down