Repository navigation
fix: Always set development mode when in development mode - #16330
Conversation
|
Kudos, SonarCloud Quality Gate passed! |
| // Ensure no older tools incorrectly detect a bundle as production | ||
| // mode | ||
| addScript(indexDocument, | ||
| "window.Vaadin = window.Vaadin || {}; window.Vaadin.developmentMode = true;"); |
There was a problem hiding this comment.
Exported web components probably also need this, so let's include it into WebComponentBootstrapHandler (or even only into BootstrapHandler) ?
There was a problem hiding this comment.
Should exported web components affect global variables on the page? They probably do it already to some degree but say that you would run a Flow app in production mode and import an exported wc that is accidentally running in development mode. Should this say that the Flow app is running in development mode?
There was a problem hiding this comment.
Should exported web components affect global variables on the page?
This shouldn't be needed and, generally, not correct IMO.
Should this say that the Flow app is running in development mode?
Definitely not, if the app is running in prod mode :)
OK, let's not touch exported wc for now 👍








No description provided.