Related issues

• Fixes STU-309

Proposed Changes

• Create a patch for the archiver third party package so it follows the symlinks when archiving directories

Testing Instructions

This can be tested using Studio or the CLI

• Apply this branch and run npm install
• Start Studio with npm start or if using the CLI run npm run cli:watch
• Create a site and inside the wp-content folder, add some symlinks for either plugins or themes (although they can be on any other folder). For example, if you download the following repo to your ~/github folder, you could add a symbolic link to it in your plugins folder using ln -s ~/github/wp-data-layer-app-pages ~/Studio/my-symlinked-website/wp-content/plugins/wp-data-layer-app-pages (replacing my-symlinked-website by your Studio site).
• Create a symlink to a file, for example, create a symlink that points to a dummy plugin file outside of the site folder, .e.g. save the following file and add a symlink to it in the plugins folder:

<?php
/**
 * Plugin Name: My Test Plugin
 * Plugin URI: https://example.com/
 * Description: A simple test plugin that doesn't do anything.
 * Version: 1.0
 * Author: Your Name
 * Author URI: https://example.com/
 * License: GPL2
 */

// Silence is golden.

• On the Studio app, navigate to Previews and create a preview site or on a terminal, open the root folder of the studio repo and run node dist/cli/main.js preview create --path ~/Studio/my-symlinked-website
• Once created, navigate to the preview site, and open /wp-admin/plugins.php or navigate to Plugins -> Intalled Plugins
• Check you can see the symlinked plugins, if you followed the example, you should see WP Data Layer App Pages and you should also see My Test Plugin, for example:
  

Test broken symlinks

• Following the steps above, delete or move the target folders and file of the symlinks so the symlinks will point to a non-existing directory and file.
• Create a preview site and make sure that there are no unexpected errors.
• Open the preview site, and confirm that you cannot see the Plugins, but you don't see any errors.

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?