Skip to main content

trackunit/iris-app v1.3.36 - Node upgraded to v22.14.0

In this version of the App SDK, we have upgraded Node to the current LTS version 22.14.0. Make sure to upgrade your workspace to at least Node v22.14.0.

If using volta, you can install the latest LTS version of Node by running:

volta install node@lts

Otherwise, you can download the latest LTS version of Node from the Node.js website.

CAN Faults API v1

Released stable version v1 of CAN Faults API. For more information, see the documentation and introduction of the endpoints.

Below is a list of all available REST endpoints:

Faults:​

➕ POST: /public/api/can-faults/faults

Get faults

Faults Summary:​

➕ POST: /public/api/can-faults/faults-summary

Get faults summary

Simulated Fault:​

➕ GET: /public/api/can-faults/simulated-faults/list

Get simulatable faults

➕ GET: /public/api/can-faults/simulated-faults/list/simulated

Get simulated faults

➕ POST: /public/api/can-faults/simulated-faults/resolve

Resolve simulated fault

➕ POST: /public/api/can-faults/simulated-faults/send

Send simulated fault

➕ GET: /public/api/can-faults/simulated-faults/summary

Get simulated faults summary

Unit ActiveFault:​

Get unit active faults

➕ GET: /public/api/can-faults/get-unit-active-faults

Get unit active faults

➕ POST: /public/api/can-faults/get-unit-active-faults

trackunit/iris-app v0.0.5 - upgrade to rspack from webpack

In this version of our Iris App SDK we have added support for Rspack as well as the existing Webpack.

To read more on rspack, please visit the rspack documentation.

Iris apps created with @trackunit/iris-app@0.0.5 should already have the required rspack configuration.

Rename and update the webpack config file​

Rename the webpack.config.ts file to rspack.config.ts and update the file to use the rspack configuration.

For the new rspack.config.ts file, you shold change the following import:

import { Configuration } from "webpack";

Change to:

import { Configuration } from "@rspack/core";

The end result should look like the following:

import { Configuration } from "@rspack/core";

export default (configuration: Configuration) => {
  return configuration;
};

Change the following entries in targets map in the project.json file of your iris app.​

For the build target, change the following:

    "executor": "@trackunit/iris-app:build",

Change to:

    "executor": "@trackunit/iris-app-sdk-rspack:build",

For the serve target, change the following:

    "executor": "@trackunit/iris-app:serve",

Change to:

    "executor": "@trackunit/iris-app-sdk-rspack:serve",

Also change the webpackConfig option to point to the new rspack.config.ts file instead of the webpack.config.ts file, and rename it to rspackConfig.

The end result should look something like the following.

  ...
  "build": {
      "executor": "@trackunit/iris-app-sdk-rspack:build",
      "options": { 
        "outputPath": "dist/apps/your_app", 
        "rspackConfig": "apps/your_app/rspack.config.ts" 
      },
      "outputs": ["{options.outputPath}"]
    },
    "serve": {
      "executor": "@trackunit/iris-app-sdk-rspack:serve",
      "options": { 
        "rspackConfig": "apps/your_app/rspack.config.ts" 
      },
      "outputs": ["{options.outputPath}"]
    },
    ...

Ownership & Visibility API

New Section: The API for managing ownership and visibility of assets has been moved to its own dedicated section.

Introduction Added: A comprehensive Introduction has been included to explain the key concepts involved in managing ownership and visibility of assets.

Endpoints: The following endpoints are now available for managing ownership and visibility of assets:

List asset shares

Share assets

Unshare assets

Transfer assets

Remove visibility

Emissions API Site Assets Update

Introducing four new endpoints to the Emissions API that allow a breakdown of assets emissions values by site summed up on a monthly basis.

These endpoints provide emissions values for the period they have been on the site. These endpoints are different from the existing monthly endpoints that provide emissions values for the period they have been in use.

Only admin users will have access to assets emissions values by site if the asset has been deleted or removed from the account.

To retrieve a list of site ids use the Sites API.

New Endpoints​

➕ GET: /v2/sites/{siteId}/emissions/monthly

Get Assets by Site Monthly

➕ POST: /v2/sites/{siteId}/emissions/monthly

Filter Assets by Site Monthly

➕ GET: /v2/sites/{siteId}/emissions/monthly/summary

Get Assets by Site Monthly Summary

➕ POST: /v2/sites/{siteId}/emissions/monthly/summary

Filter Assets by Site Monthly Summary

Emissions API v1 Removed

The Emissions API v1 has been removed. All endpoints have been deprecated and will no longer be available. Please use the Emissions API v2 for all emissions data.