https://superuser.com/questions/179660/how-to-recursively-delete-directory-from-command-line-in-windows
This removes the directory C:\test, with prompts :
rmdir c:\test /s
This does the same, without prompts :
rmdir c:\test /s /q
Regarding the sudo part of your question, if you need more priviliges, you can first open a new shell as another user account using the runas command, like this:
runas /user:Administrator cmd
rmdir c:\test /s /qhttps://forum.ait-pro.com/forums/topic/constant-wp_memory_limit-already-defined-in-wp-config-php-on-line-130/
This problem is caused by a Theme that added this WP code/constant: define('WP_MEMORY_LIMIT', '512M'); at the bottom of the wp-config.php file after the require_once(ABSPATH . 'wp-settings.php'); code in the wp-config.php file. No code is supposed to go after this line of code in the wp-config.php file. All custom code in the wp-config.php file needs to be above this line of code.
https://support.gatsbyjs.com/hc/en-us/articles/4402066361619-Upgrade-Gatsby-Version-on-Gatsby-Cloud
Occasionally you'll want to upgrade your gatsby version to take advantage of new features or recent bug fixes. This guide explains what you need to do to upgrade your gatsby version on Gatsby Cloud.
First specify the gatsby dependency version in your package.json file.
This step is only necessary if you commit a lock file to your remote repository. You'll need to run npm install or yarn install to update your package-lock.json or yarn.lock file to ensure your gatsby version is not locked to an earlier version than you intended.
Finally, commit the updated package.json and lock file (if necessary) to your remote repository. After this, the next Gatsby Cloud will install the new gatsby version on the next build.
You can see which version of gatsby is in use by viewing the Raw Logs for your build after performing the update.
