Skip to content

NODE_ENV not working for different build environments #244

Open
@droidscout

Description

@droidscout

Hi there!

I've noticed that setting the NODE_ENV variable to something other than "production" doesn't takes the nodejs runtime mode into account.

My package.json has the following scripts added:
"scripts": {
"ng": "ng",
"start": "ng serve",
"build": "ng build",
"production": "ng build --configuration=production",
"integration": "ng build --configuration=integration",
"development": "ng build --configuration=dev",
"run_dev": "ng serve --configuration=dev"
}

When passing either NODE_ENV=integration or event NODE_ENV=development it just downloads the package dependencies but never builds the source.

Is this an intended use case for the sources not being built? If that's the case, then s2i build would only create a container with the source code and it's dependencies.

Stay safe and all the best,
Ralph

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