Update a project's JavaScript library

Each ADT project keeps one shared copy of the @adt/fmdapi JavaScript library at vendor/@adt/fmdapi. Every Web Viewer app in the project uses that copy. Updating it replaces the project's vendored files with the version included in the ADT installation on your computer.

Update the library

Ask your coding agent to update the project's ADT JavaScript library:

Copy 
Update this project's ADT JavaScript library and review the resulting changes.

The agent runs the update from a Web Viewer app directory. ADT replaces vendor/@adt/fmdapi and keeps the workspace dependency pointed at the vendored package.

Because the library is committed project source, review its changes with the rest of your work. An update can change runtime behavior, exported types, or APIs used by every Web Viewer app in the project.

Check every app in the project

Run the project's normal checks after the update. A project with several Web Viewer apps should check each app because they all consume the same library but can use different parts of its API.

If an update reports a type or API error, update the affected application code to match the installed library version. Do not edit the generated or vendored files to hide the error.

Regenerate types only after schema changes

Updating @adt/fmdapi does not require Typegen by itself. Regenerate an app's client only when its FileMaker database schema changes, including changes to configured fields, value lists, or portals.

See Generate types with Typegen for the schema-generation workflow.

The JavaScript library is separate from the global ADT installation and the ADT components inside a FileMaker file. Updating one does not update the others.