this._resolve is not a function about zero-md HOT 4 CLOSED

Hi - thanks for highlighting this. I believe it's a bug because I didn't handle the edge case whereby an instance may be disconnected, then reconnected again, without being re-instantiated.

Internally, there are 2 pre-requisites before zero-md can begin its rendering op:

1. Marked and Prism must be loaded; and
2. The instance must be connected.

The waitForReady() function basically ensures that these 2 conditions are met.

I'll try to think of a better way to handle this and roll-out a bug fix soon. At the same time, I'll remove the (non-standard) JSON import so that you should be able to consume via the recommended way:

import ZeroMd from 'zero-md'

customElements.define('zero-md', ZeroMd)

render() {
  ...
}

Thanks again!

from zero-md.

Hi @jonmann20 - fixed it! Could you kindly help see if the issues are resolved? The latest version v2.1.0-rc.1 is in pre-release so if you could run this:

npm i -D zero-md@next

then consume using:

import ZeroMd from 'zero-md'

customElements.define('zero-md', ZeroMd)

render() {
  ...
}

and let me know if anything else crops up? 🙏

from zero-md.

Worked perfect, thanks for the quick response!

from zero-md.

Thanks for bringing this issue up! This should be fixed with the latest release. I'll mark this issue as closed for now - but do re-open this if it happens again. 🍻

from zero-md.