Question: Microsoft has some [decent documentation](https://learn.microsoft.com/en-us/microsoft-edge/extensions/guides/debugging-extensions#content-script-debugging) on debugging Content Scripts for an Edge Extension and the top of the page even includes a [Channel 9 video](https://channel9.msdn.com/Blogs/One-Dev-Minute/Debugging-Microsoft-Edge-Extensions) on the subject.

Unfortunately, the techniques [no longer seem to work](https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/13829248/), as even when following the debug instructions and using the the [sample Text Swap extension](https://github.com/MicrosoftEdge/MicrosoftEdge-Extensions-Demos), the extension and content script never show up in the debugger. 

[![Screenshot of Edge running Text Swap extension](https://i.stack.imgur.com/F1ShJ.png)](https://i.stack.imgur.com/F1ShJ.png)

As you can see from the screenshot, the content script has run (and changed the font on the page) but it and the extension itself are nowhere to be seen in the debugger.

Anyone figured out how to get the content script to show up in the debugger?

Answer: 
The answer is no. You only need one.

NPM modules can be incorporated into your code several folders down in your project.

Take for example a project folder:

```
/root
   app.js
   package.json
   /public
      index.html
   /node_modules
      ...

```

All modules in the `node-module` folder can be used in any project sub-folder.

Say, you have a file named `anotherApp.js` in a folder down the line, it will 'inherit' all node modules installed in any parent folder. Therefore, it will also be able to access every module that is in the project root `node_module` folder.

```
/root
   /somefoldername
      /anotherfolder
         /application
            anotherApp.js
   /node_modules
      ...

```

I should add, that NPM (Node package manager) is there to handle locally installed modules. The `fs` (File System) modules does come with node and is installed as a global, therefore you do not need to install it via NPM. Check out <https://www.npmjs.com/> for a full list of available downloadable modules.
I would always suggest using `git` to synchronize your local files and your files on the EC2 server. 

To install the same dependency on both your local and cloud, you can save it in your `package.json`
e.g. `npm install --save express` 

And on your server, `npm install` would install all the dependencies listed in `package.json`