# Sage Update on Wordpress Questions

**URL:** https://discourse.roots.io/t/sage-update-on-wordpress-questions/23311
**Category:** sage
**Tags:** sage9
**Created:** 2022-06-08T16:45:36Z
**Posts:** 6
**Showing post:** 4 of 6

## Post 4 by @strarsis — 2022-06-08T18:40:59Z

The **build dependencies** , as they are `node`-based reside in `node_modules/` in theme directory.  
Those shouldn’t be listed via SFTP though, as it is bad practice (as aforementioned) to have build dependencies on the server. But if they are listed, don’t just delete them, as there may be the rare but possible case (of even worse practice) that the theme includes files from `node_modules/`.

The **runtime dependencies** (if the `Sage` version uses them, Sage `8` doesn’t require runtime libraries via `composer`), managed by `composer`, reside in `vendor/` in theme directory. There is an exception for Sage `10` though where the `acorn` runtime alternatively may also be added as a WordPress mu-plugin or a plugin instead as a `composer` library of the theme.

If you plan to develop on the themes, don’t do this on the production system. Download everything (including the data/uploads and database dumps) and either use something like `Trellis` VM feature or a `Docker` container or other development system locally on your workstation.  
And put everything into version control (`git`) first. Ideally you can contact the original developers and get the repository with full history. I also encountered sites where the `.git` directory was also on the server (which is also bad practice, as the released app/theme should be just the workspace with as little files as possible).

If you want to update your `Sage` `9` theme, you may be interested in this update guide for `Sage` `9`:

e class='quote' data-post="2" data-topic="22287"\> 
 ![](https://discourse.roots.io/user_avatar/discourse.roots.io/strarsis/48/4543_2.png)
[No dist folder output on updated Sage 9 theme](https://discourse.roots.io/t/no-dist-folder-output-on-updated-sage-9-theme/22287/2) [sage](/c/sage/11)

> Have you upgraded your old Sage 9.x theme to webpack 5 using the latest commit in Sage 9 branch of [Sage repository](https://github.com/roots/sage)? Have you applied this Theme update approach (previously used for the Sage 9.x update branch ([Sage "9.1": Please test](https://discourse.roots.io/t/sage-9-1-please-test/20067)))? Updating an existing Sage 9 theme (quick guide) Create a new Sage 9 project with the command above, select the framework that is also used by your own Sage 9 project. (It is assumed that your own Sage project is already under version control (as git). Copy a…

Edit: The build dependencies can be (re)installed just from the `package.json`; `package-lock.json`/`yarn.lock` (by `npm install`/`yarn install)`, the runtime dependencies from `composer.json`; `composer.lock` (by `composer install`). The `npm` and `composer` dependencies are downloaded by their respective package managers.

---

_[View the full topic](https://discourse.roots.io/t/sage-update-on-wordpress-questions/23311)._