What are ChasePlane JS modules and how do I install them in MSFS?
Learn what ChasePlane JS and Bridge modules do, where they belong in MSFS 2020/2024, how to install them and fix missing-module errors.
ChasePlane JS modules are in-simulator JavaScript packages that let the Windows ChasePlane app exchange camera and aircraft-state data with Microsoft Flight Simulator. Install them through ChasePlane’s installer for the correct MSFS 2020 or 2024 Community folder; do not copy the desktop application itself into Community.
What do the ChasePlane JS and Bridge modules do?
They provide the simulator-side half of ChasePlane’s camera connection. The desktop application cannot perform every camera operation through SimConnect alone, so the JavaScript module runs inside Microsoft Flight Simulator and passes the required commands and state through the Bridge.
| Component | Purpose | Where it belongs |
|---|---|---|
| ChasePlane desktop app | Provides the user interface, camera controls and profile management | A normal Windows application location |
| JS module | Runs within MSFS and handles simulator-side camera communication | The active MSFS Community folder, deployed by the installer |
| Bridge | Relays messages between MSFS and the desktop process | Where the ChasePlane installer places it; do not relocate it manually |
JS means JavaScript, not Java. You do not need to install a Java runtime, Node.js or a browser extension. These are support components rather than aircraft, so they will not appear in the aircraft selection screen.
How do I install ChasePlane JS modules in MSFS?
The reliable method is to let ChasePlane’s own installer or updater deploy the matching integration rather than downloading or assembling module folders manually.
- Close MSFS and ChasePlane. Installing while the simulator is running can leave the old module loaded until the next restart.
- Install or update the desktop application. If ChasePlane itself is not set up yet, follow our complete ChasePlane installation process for MSFS 2020 and 2024 first.
- Select the correct simulator edition. Choose MSFS 2020 or MSFS 2024 when the installer offers simulator integrations. Each edition can use a different Packages and Community location.
- Confirm the active Community folder. Select
Communityitself, not its parentPackagesfolder and never theOfficialfolder. - Install or repair the simulator integration. Allow the installer to deploy both the JS and Bridge components. If they are already shown as installed, use the installer’s repair or reinstall option.
- Check the package depth. A simulator package should have files such as
manifest.jsonandlayout.jsonin its package root, not buried inside an extra archive or duplicate folder. - Restart and test in a flight. Start Microsoft Flight Simulator, load an aircraft and then open ChasePlane. A connection may not be fully established while MSFS is still loading or sitting at an early menu screen.
Only copy modules manually if your ChasePlane build explicitly supplies unpacked package folders and instructions for doing so. Do not place the ChasePlane executable, installer or a ZIP archive in Community.
Where should the modules be installed?
The simulator-facing packages belong in the Community folder MSFS is actually using, which is not always the first Community folder found by a Windows search.
Microsoft Store, Steam and custom installations can have different package paths. MSFS 2024 can also use a location separate from MSFS 2020; our MSFS 2024 ChasePlane setup notes explain why selecting the active Packages location matters.
A mistake we see constantly is installing the modules into an abandoned Community folder left by an earlier installation. Another is nesting them as Community/package-name/package-name/manifest.json. MSFS expects the actual package root directly under Community unless an add-on management tool has created a valid link there.
Why does ChasePlane say the JS module is missing?
A missing-module warning usually means MSFS did not load the package or the Bridge cannot reach the desktop application.
- Wrong Community folder: run the ChasePlane repair process and select the location used by that exact simulator edition.
- MSFS Safe Mode: Safe Mode suppresses Community add-ons, including ChasePlane’s simulator integration. Restart normally before testing.
- Nested or unextracted files: extract the package fully and remove any extra directory level.
- Mixed component versions: update the desktop app and reinstall its integration together. An older JS module may not communicate correctly with a newer Bridge.
- Duplicate packages: remove obsolete copies from other Community or linked add-on folders, then repair the integration once.
- Security software interference: check whether the Bridge was quarantined or blocked from local communication. Restore and allow the legitimate ChasePlane component rather than disabling protection globally.
If the packages are in the correct location but ChasePlane remains disconnected, work through our module and SimConnect connection checks.
Can ChasePlane JS modules be installed on Xbox or PlayStation?
No. ChasePlane requires its external Windows desktop application, Bridge and access to simulator package files. Those components cannot be installed on Xbox Series X|S or on the PlayStation 5 versions of MSFS 2024, so ChasePlane’s JS integration is PC-only.