We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
[@zenuml/core] Store is a function and is not initiated in 1 second.
The @mermaid-js/mermaid-cli program uses @mermaid-js/mermaid-zenuml as a dependency, which then uses @zenuml/core.
@mermaid-js/mermaid-cli
@mermaid-js/mermaid-zenuml
@zenuml/core
It sounds like a [@zenuml/core] Store is a function and is not initiated in 1 second. warning is being logged due to the following line of code:
zenuml-core/src/store/Store.ts
Lines 14 to 21 in 7658a1c
This warning is causing some confusion with @mermaid-js/mermaid-cli users (see mermaid-js/mermaid-cli#588), and it makes our test logs messier.
It looks like a timer is started whenever @zenuml/core is imported, and that warning is automatically printed if ZenUML isn't used within 1 second.
Is there any chance we can remove this warning, or at least hide it by default?
The text was updated successfully, but these errors were encountered:
Bumping this, would love to have this option
Sorry, something went wrong.
No branches or pull requests
The
@mermaid-js/mermaid-cli
program uses@mermaid-js/mermaid-zenuml
as a dependency, which then uses@zenuml/core
.It sounds like a
[@zenuml/core] Store is a function and is not initiated in 1 second.
warning is being logged due to the following line of code:zenuml-core/src/store/Store.ts
Lines 14 to 21 in 7658a1c
This warning is causing some confusion with
@mermaid-js/mermaid-cli
users (see mermaid-js/mermaid-cli#588), and it makes our test logs messier.It looks like a timer is started whenever
@zenuml/core
is imported, and that warning is automatically printed if ZenUML isn't used within 1 second.Is there any chance we can remove this warning, or at least hide it by default?
The text was updated successfully, but these errors were encountered: