Electrode Native
v0.41
v0.41
  • Introduction
  • INTRODUCTION
    • Overview
      • What is Electrode Native
      • Why use Electrode Native
      • What is a MiniApp
      • Electrode Native workflow
      • Native dependencies management
      • JS/Native communication
      • Requirements
      • Upgrading Electrode Native
      • Contributing
  • REFERENCE
    • Bundle Store
    • Composite
    • Container
      • What's inside
      • Publication
      • Integration
      • Initialization
      • Launching MiniApps
    • Cauldron
      • Structure
      • Setup
      • Compatibility checks
      • Guidelines
    • Manifest
      • Override
      • Native Modules
      • Configurable Modules
    • Runner
    • APIs
      • Project Generation
      • Implementation
      • Versioning
      • Guidelines
    • Bridge
      • Message Types
      • Communication
      • Leveraging APIs
    • CLI
      • Global CLI
      • Local CLI
    • GLOSSARY
  • GUIDES
    • Debugging multiple MiniApps
  • CLI COMMANDS
    • add
    • bundlestore
      • create
      • delete
      • upload
      • use
    • binarystore
      • add
      • get
      • remove
    • code-push
      • patch
      • release
      • promote
    • compat-check
    • create-api-impl
    • create-api
    • create-composite
    • create-container
    • create-plugin-config
    • publish-container
    • transform-container
    • create-miniapp
    • link
    • regen-api
    • regen-api-impl
    • run-android
    • run-ios
    • start
    • unlink
    • upgrade-miniapp
    • cauldron add
      • file
      • jsapiimpls
      • miniapps
      • nativeapp
    • cauldron config
      • get
    • cauldron del
      • file
      • jsapiimpls
      • miniapps
      • nativeapp
    • cauldron get
      • config
      • dependency
      • nativeapp
    • cauldron repo
      • add
      • clear
      • current
      • list
      • remove
      • use
    • cauldron update
      • file
      • jsapiimpls
      • miniapps
      • nativeapp
    • cauldron batch
    • cauldron regen-container
    • cauldron upgrade
    • cauldron why
    • github
      • github create-ref
      • github delete-ref
      • github align-dependencies
    • platform
      • plugins
        • list
        • search
      • config
        • set
        • get
        • del
        • list
      • install
      • versions
      • uninstall
      • use
Powered by GitBook
On this page
  • Description
  • Remarks
  • Syntax
  • Options
  • Related commands
  1. CLI COMMANDS
  2. bundlestore

upload

PreviousdeleteNextuse

Last updated 4 years ago

This command can only be used with access to an

To use this command, the bundleStore config must be set in cauldron

Description

Upload a JS bundle to the current store.

Remarks

  • Both iOS and Android bundles will be generated and uploaded to the store by default. If you only need to upload a bundle for a single platform, use the --platform option.

  • By default development bundle(s) will be generated. If you rather need to upload a production bundle you can use the --prod flag.

  • There are three different ways to generate and upload a bundle :

    • Using a Cauldron, by providing a descriptor and eventually some extra JS dependencies (--descriptor/--extraJsDependencies option)

    • By manually specifying all the MiniApps/JS API Implementations and extra JS dependencies to put in the bundle (--miniapps/--jsApiImpls/--extraJsDependencies options)

    • From a metro server (packager) running locally (--fromPackager flag)

Syntax

ern bundlestore upload

Options

--baseComposite <compositePath>

--descriptor/-d <descriptor>

  • Generate and upload a JS bundle out of all the MiniApps/JS API implementations associated to this complete native application descriptor.

  • Mutually exclusive with --miniapps/--jsApiImpls options.

--extraJsDependencies/-e <dependencies>

  • Add extra JavaScript dependencies to the JS bundle to upload.

  • Can be used in combination with --descriptor or --miniapps/--jsApiImpls options.

--fromPackager

  • Get and upload the bundle served by the current local metro server (packager).

  • A metro server must be running on localhost:8081 in order to use this flag.

  • Mutually exclusive with --descriptor/-miniapps/jsApiImpls/extraJsDependencies options.

--fromGitBranches

  • Create Composite using the latest commits made to each of the MiniApp branches (HEAD), rather than using the MiniApps SHAs that are inside the current Container version.

  • Can only be used in combination with the --descriptor option.

  • This flag will be ignored if the target descriptor does not contain any MiniApps tracking git branches

    Default false

--jsApiImpls

  • One or more JS API implementation(s) to add to the JS Composite project.

  • The JS API implementation(s) passed to this command can be a valid Yarn package format or a Git format or file scheme.

  • Mutually exclusive with --descriptor option.

--miniapps/-m <miniapps>

  • One or more MiniApps to add to the JS Composite project.

  • The MiniApps passed to this command can be a valid Yarn package format or a Git format or file scheme.

  • Mutually exclusive with --descriptor option.

--platform

  • Set this option to generate and upload bundle for a single platform.

  • Either android or ios.

  • If this option is not provided, both iOS and Android bundles will be generated and uploaded.

--prod

  • Set this flag to geenrate and upload a production bundle.

  • If this flag is not set, a development bundle will be generated and uploaded.

--resetCache\

  • Indicates whether to reset the React Native cache prior to bundling

  • Default false

Related commands

Git or File System path, to the custom Composite repository (refer to the documentation for more information).

| Create a store | Use a specific store | Delete a store

Electrode Native bundle store server
custom Composite
bundlestore create
bundlestore use
bundlestore delete