How dickmans/plm-extensions works
Project type and purpose
• This is a full-stack Node.js/Express web application providing a suite of PLM (Product Lifecycle Management) extensions that integrate with Fusion Manage and Autodesk Platform Services (APS).
• The README calls out features such as Change Impact Analysis, Class Browser, Data Manager, MBOM Editor, etc., all delivered as web “apps” or “portals” using APS authentication (PKCE) and API calls to Fusion Manage.
File structure
• Top‐level
• app.js (Express app entry)
• bin/www (HTTP(S) server startup)
• package.json (dependencies, scripts)
• settings.js + settings/ (tenant‐specific config)
• keys/ (TLS certs for HTTPS)
• uploads/ (file store)
• MVC pattern
• routes/ (controllers for landing, pdm, plm, services)
• views/ (Pug templates organized by category: addins, apps, admin, docs, framework, tutorial, dev)
• public/ (static assets: javascripts, stylesheets, images, fonts, service worker)
• No local database—data is fetched from APS/Fusion Manage.
• Deployment/config files: .gitignore, .vscode, manifest.json, sw.js.
README
• Confirms PKCE authentication, need for APS “Desktop, Mobile, Single‐Page App” client ID in settings.js.
• Lists all extensions (“apps”) and video links—these map to individual front‐end modules under public/javascripts/apps and views/apps.