Skip to content

corber start initializes with environment undefined #681

Description

@caljess599

In our environment.js settings, we want to define build-environment-dependent settings for corber, like so:

if (environment === 'development' && process.env.CORBER ) {
        ... 
}

But corber start fails because the value of environment is for some reason undefined at this point and thus none of the conditionals match.

A workaround is to first define the minimum settings to pass validation:

if (process.env.CORBER) {
        ENV.locationType = 'hash';
        ENV.rootURL = '';
};

Simple enough, but it strikes me that this might be a bug?

(FWIW, I don't believe that corber build has this issue.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions