Documentation
vuepress-migration
developPrimary versionrte_2xvuepress-migration
vuepress-migration
developPrimary versionrte_2xvuepress-migration
  • Cubbles documentation
  • First steps
    • Generate a project
    • Create a webpackage
    • Create an elementary component
    • Create a compound component
      • Compound slot initialization
  • Runtime extension - RTE
    • User guide
      • RTE Integration
      • The Cubbles TAG API
        • The Cubbles Dependency API
      • The Cubbles Javascript API
        • Interacting with Cubbles from the outside
        • Adding dynamic connections
        • Interacting with Elementary Cubbles from the inside
      • The RTE Processing
        • RTE initialization and rendering timeline
      • The Cubbles IFrame API
        • The Cubbles IFrame Resizer API
      • The Cubbles mutation based start event API
      • FAQs
        • How to manually resolve dependency conflicts?
        • How to create a component instance dynamically?
        • How to render HTML Markup coming from input slot?
        • How to replace a dependency when declaring a component instance?
        • How to synchronize multiple dataflows between component instances?
        • How to handle the copyValue flag for non serializable instances?
    • Contributor guide
      • CIF processing
  • Developing with the vanilla boilerplate
    • Creating a new project
    • Developing elementaries using the vanilla boilerplate
    • Developing compounds using the vanilla boilerplate
    • Using the vanilla boilerplate scripts
  • Coder devtools - CDT
    • User guide
      • Create Cubbles artifacts
      • Upload a Webpackage
      • Generate a README file
      • Rename an artifact
      • Configure network proxy
      • Validate the manifest.webpackage file
      • Change active webpackage
      • Bulk upload of webpackages
      • Release a webpackage
      • Update the RTE version of a webpackage
      • Prepare a webpackage to be released
      • Update webpackage to the next development version
      • Generate a test environment for a component
      • Testing Cubbles components
      • Validate sources
      • Create a demo webpackage
    • Contributor guide
      • Checklist for releasing a new webpackage.modelVersion
  • Terms and concepts
    • Webpackage
    • Artifacts
    • User roles
    • Base
Powered by GitBook
On this page
  • Purpose
  • Steps
  • Outcome
  1. Coder devtools - CDT
  2. User guide

Validate the manifest.webpackage file

PreviousConfigure network proxyNextChange active webpackage

Last updated 5 years ago

As you may know, the manifest.webpackage file must follow a according to its model version. The offers you the +webpackage-validateManifestFile task to validate the manifest of your current webpackage automatically.

Note that the manifest is validated before being , and if it is not valid the upload will be interrupted.

Purpose

To show how to validate the manifest of a webpackage using the +webpackage-validateManifestFile` task.

Steps

You should run the task within the CDT folder (normally it is called devtools) as follows:

grunt +webpackage-validateManifestFile

Outcome

If the manifest has errors, those will be prompted. Otherwise, you will get a message similar to the one below:

Done, without errors.
JSON schema
CDT
uploaded