Skip Pruning

When deploying a Node.js application, if the NODE_ENVenvironment variable hasn’t been set to production, you may see the following warning:

Skip Pruning Because NODE_ENV is Not ‘Production’

This occurs because the NODE_ENV variable isn’t set to production by default during application creation.

To resolve or prevent this issue, manually add the NODE_ENV environment variable when adding your application or in your application’s Environment variables. If you add the environment variable after the application has been created, you can redeploy it using Deploy changes.

Was this article helpful?

© 2013 - 2025 Kinsta Inc. All rights reserved. Kinsta®, MyKinsta®, and DevKinsta® are trademarks owned by Kinsta Inc.The WordPress® trademark is the intellectual property of the WordPress Foundation, and the Woo® and WooCommerce® trademarks are the intellectual property of WooCommerce, Inc. Uses of the WordPress®, Woo®, and WooCommerce® names in this website are for identification purposes only and do not imply an endorsement by WordPress Foundation or WooCommerce, Inc. Kinsta is not endorsed or owned by, or affiliated with, the WordPress Foundation or WooCommerce, Inc. Legal information