Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Angular enableProdMode gets ignored #28373

Closed
kroeder opened this issue Jun 27, 2024 · 0 comments · Fixed by #28415
Closed

[Bug]: Angular enableProdMode gets ignored #28373

kroeder opened this issue Jun 27, 2024 · 0 comments · Fixed by #28415

Comments

@kroeder
Copy link
Member

kroeder commented Jun 27, 2024

Describe the bug

I noticed Angular didn't print a couple of expected errors on console and I also haven't seen the typical "Angular is running in development mode." (or something similar)

A quick research showed, that you can properly set enableProdMode, it also is correctly read from the builder config but it is ignored later on after all.

Workaround: set NODE_ENV=development before running Storybook.

Reproduction link

https://stackblitz.com/edit/github-hxakzq?file=angular.json

Reproduction steps

  1. Start storybook
  2. See missing "Angular is running in development mode." in console.

System

System:
    OS: Linux 5.15 Ubuntu 22.04.4 LTS 22.04.4 LTS (Jammy Jellyfish)
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz
    Shell: 5.8.1 - /usr/bin/zsh
  Binaries:
    Node: 20.15.0 - ~/.nvm/versions/node/v20.15.0/bin/node
  npmPackages:
    @storybook/addon-a11y: ^8.1.10 => 8.1.10 
    @storybook/addon-essentials: ^8.1.10 => 8.1.10 
    @storybook/addon-interactions: ^8.1.10 => 8.1.10 
    @storybook/angular: ^8.1.10 => 8.1.10 
    @storybook/blocks: ^8.1.10 => 8.1.10 
    @storybook/icons: ^1.2.9 => 1.2.9 
    @storybook/test: ^8.1.10 => 8.1.10 
    @storybook/theming: ^8.1.10 => 8.1.10 
    chromatic: ^11.5.4 => 11.5.4 
    eslint-plugin-storybook: ^0.8.0 => 0.8.0

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants