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

feat: add NITRO_TIMING env support #184

Closed
wants to merge 1 commit into from
Closed

feat: add NITRO_TIMING env support #184

wants to merge 1 commit into from

Conversation

atinux
Copy link
Collaborator

@atinux atinux commented May 3, 2022

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

I found it useful to debug in production by simply setting NITRO_TIMING=1 env variable πŸš€

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@atinux atinux changed the title feat: add NITRO_TIMING env support feat: add NITRO_TIMING env support May 3, 2022
@pi0
Copy link
Member

pi0 commented May 4, 2022

We can properly support config override with env for all keys with (unjs/c12#16). In the meantime, you can use timing: Boolean(process.env.NITRO_CONFIG_TIMING) inside nitro config.

@pi0 pi0 closed this May 4, 2022
@pi0 pi0 deleted the feat/timing branch May 4, 2022 09:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants