App packages overview
Previously, developers could only bind and maintain a single source file to an
<html/>component within OXIDE (by uploading it as an asset). With app packages, developers can maintain large custom HTML projects in OXIDE very easily, thereby improving developer productivity.
The high level architecture of app packages is outlined below.
App packages architecture
- 1.A package is created from a template and source files can now be edited.
- 2.A developer triggers a deploy which sends all the source code over to the JourneyApps build system.
- 3.The JourneyApps build system starts building the app, and looks for app packages.
- 4.For each app package, the JourneyApps build system will execute the
buildcommand inside each corresponding
distdirectories and other build artifacts are created, but are hidden to the developer.
- 6.The build artifacts are packaged along with the compiled application and uploaded to the update system.
- 7.The JourneyApps Runtime downloads the application update along with the compiled package's build artifacts, and they are executed inside your code.
- 8.Some components such as
<html/>component can display build artifacts from an app package such as an
- 1.packages are defined inside the
/packagesdirectory in your application's project files.
- 2.A package will always contain a single
scriptssection that contains a
- 4.A name that starts with
The initial release of packages will only be useable from within your app (i.e. the JourneyApps Runtime), but in the near future, packages will also be useable inside CloudCode tasks. This will enable you to write code that can be shared across the app as well as in CloudCode.
OXIDE includes a number of package templates. These are listen when creating a new package:
Use this package to easily create PDF reports that can be dynamically generated from within the app and rendered offline inside an
<html>component. To learn more about this template, and to see an example on how to use it, follow this guide.
Upon deploying your app.
App modules are lightweight ways to share code between views in your app. App packages can also be used to share code, however they also provide a way to run custom build commands upon a “deploy” action, and can also generate assets that can then be used in your app.
Static assets which are uploaded directly to the app, are simply copied in when the app is deployed, and accessible when the app runs.
Assets that are copied into packages are not directly accessible unless they go through a compilation step. Some packages such as the ones which use the PDF template as a base, contain a webpack file which compile the assets and make them accessible to the rest of the app.