The eWizard.js framework builders write the framework and the builder versions in the resulting build. The files where these versions are written depend on the builder and the item type.
The following builds are available for viewing the versions:
• Local build
• Export to the target system
Local build version
The eWizard.js framework writes the versions of the builder and framework when generating the local build using eWizard CLI.
• Build the project locally using wiz dev or options: wiz dev --live or wiz dev -watch.
• Open any of the JS files from the ./build/dev/ directory in your code editor: index.js, app.js, etc.
The eWizard.js writes the builder and framework versions as the comments in the beginning of the file.
For example, this is the version comment in the email build:
/*! builder: dev-builder - version: 3.23.3 framework: ewizardjs - version: 5.5.1 */
(function webpackUniversalModuleDefinition(root, factory) {
if (typeof exports === "object" && typeof module === "object") module.exports = factory(require("Content")["app"]); else if (typeof define === "function" && define.amd) define([], factory); else if (typeof exports === "object") exports["index"] = factory(require("Content")["app"]); else root["Content"] = root["Content"] || {},
root["Content"]["index"] = factory(root["Content"]["app"]);
}This is the example of the version comment in the e-Detailer build:
/*! * builder: dev-builder - version: 3.20.1 * framework: ewizardjs - version: 5.3.2 */ (function webpackUniversalModuleDefinition(root, factory)
Export build version
To generate the production build, you need to export your project for one of the target systems using the eWizard platform. eWizard.js writes the builder and framework versions depending on the item type:
• For emails, eWizard.js writes the versions in the resulting HTML file and creates the banner.txt file.
• For e-Detailers, eWizard.js writes the versions in the resulting app.js file.
Email HTML export
The eWizard.js framework writes the versions of the builder and framework when generating the email or email fragment build.
• Export your email for the target system using the eWizard platform.
• Open the HTML file in the root directory of the resulting email build with your code editor.
The builder and framework versions are written as the HTML comments. For example:
<!-- builder: email-templates-builder - version: 2.39.2 framework: ewizardjs - version: 5.5.2 -->
<!DOCTYPE html><html xmlns="http://www.w3.org/1999/xhtml" xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office"><head> <meta charset="utf-8"> <title>Document</title><!-- builder: email-templates-builder - version: 2.39.2 framework: ewizardjs - version: 5.5.2 --> <style></style></head><body style="margin:0;padding:0;background:#fff;"> </body><script src="./js/mi-api.bundle.js"></script></html>
NOTE: The versions in the build exported for Veeva Vault are written at the end of the HTML file.
Write framework version in the email settings
To activate/deactivate writing versions in the exported email HTML file, add the writeFrameworkVersion field to the settings.json file in the email project before exporting:
• false — to deactivate writing the version.
• true — for writing the version. It's the default value.
// ./settings.json{
"name": "Viseven-email-template",
"writeFrameworkVersion": false
}TIP: This feature is useful when you want to reduce the size of your HTML email markup.
When you're exporting your email project, eWizard.js adds the banner.txt file to the email export directory. This file contains the builder and framework versions. The eWizard.js frameworks adds this file to the export directory regardless of the writeFrameworkVersion settings.
e-Detailer export
The eWizard.js framework writes the versions of the builder and framework when generating the build for e-Detailers. For this, do the following:
1) Export your e-Detailer to the target system using the eWizard platform.
2) Open the app.js file in the root directory of the resulting build using your code editor.
The builder and framework versions are written as the comments. For example:
/*! builder: viseven-spa-builder - version: 1.7.4 framework: ewizardjs - version: 5.5.1 */