Hide the [@zenuml/core] Store is a function and is not initiated in 1 second. warning

[aloisklink]

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

	let storeInitiationTime: number = 0;
	setTimeout(function () {
	if (!storeInitiationTime) {
	console.warn(
	"[@zenuml/core] Store is a function and is not initiated in 1 second.",
	);
	}
	}, 1000);

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?

[l1n]

Bumping this, would love to have this option

[db4rr]

I also support this

[m1rm]

maybe this #193 helps to reduce the confusion. My intention was to make the warning sound like a warning and not like an error

[MrCoder]

This warning, originally put in place due to issues with clients having to initialise the store manually, is no longer relevant. These issues were prevalent in the early days, but our new API has largely eliminated the prospect of the store not initializing. have removed the warning via this pull request: #194.

[MrCoder]

Fixed in https://www.npmjs.com/package/@zenuml/core/v/3.24.13

[dontry]

Hi @aloisklink, do you want me to bump @zeuml/core version to the latest in the @mermaid-js/mermaid-zenuml dependencies?

[aloisklink]

Hi @aloisklink, do you want me to bump @zeuml/core version to the latest in the @mermaid-js/mermaid-zenuml dependencies?

It should be fine, since the current ^3.23.27 supports 3.24.13.

https://github.com/mermaid-js/mermaid/blob/d16e46a3860bce8c4ae1d12308c5d9cf8055bcf7/packages/mermaid-zenuml/package.json#L36

I think one of the automated @renovatebot PRs like mermaid-js/mermaid#5961 will bump the pnpm-lock.yaml file and therefore the version used for tests, but since it won't update the package.json file, there won't be a need for an update.