#### **Background**
We want to develop a second recommendation experiment within the Chrome extension, placing recommendation cards alongside articles using the MoreLike API.
Once the experiment is ready, deploy to the existing Chrome extension.
#### **User Story**
As a product team, we need to deploy the new recommendation experiment within the Chrome extension to test its performance and gather user interaction data for further analysis.
#### **Requirements**
Deploy the new recommendation experiment to the existing Chrome extension.
Technical Notes:
The extension has separated experiments in folders that mimic ResourceLoader module naming conventions. The first experiment lives in the folder `src/content_scripts/vector2022.empty.search` . The `main.js` file in that folder is loaded onto the page by importing it in `injector.js` and injecting in onto the page via a <script> tag.
In order to disable that experiment, we have to remove it from the injector.js script and replace it with a new script.
```name=injector.js,lang=js
import main from './vector2022.empty.search/main?script&module'; 馃憟 // replace this file with a new experiment
const scriptTag = document.createElement( 'script' );
scriptTag.src = chrome.runtime.getURL( main );
scriptTag.setAttribute( 'defer', 'defer' );
scriptTag.setAttribute( 'type', 'module' );
document.body.appendChild( scriptTag );
```
####**Acceptance Criteria**
- Successfully deploy the experiment in the Chrome extension.
- The experiment must be fully functional as per requirements.
- Instrumentation is set up and tracking correctly.
- No regression or negative user impact is observed.
- Flag any issues or unknowns during the deployment process and address them.
#### **Communication**
Announcements or internal discussions should be held if necessary to inform stakeholders.
#### **Rollback Plan**
Ensure a defined rollback plan is in place if any issues arise in production after deployment.