TypeError: Cannot read property 'block' of undefined at Function.markdownItContainer about quasar-ui-qmarkdown

[SouthRibbleTech]

@hawkeye64 I can also confirm that this is working again. Thank you.

[mesqueeb]

Fixed it by doing: no-container="true"

not sure what the bug is though.

[hawkeye64]

yeah, I have no idea. Will investigate.

[hawkeye64]

I'd say, please use yarn and see if the issue persists. Don't forget to remove node_modules and package.lock (or, whatever it's called) file.

[hawkeye64]

@mesqueeb By chance do you have two separate instances of QMarkdown being loaded? One being used by one component and another used by a different component?

[hawkeye64]

Have a feeling markdownItContainer is doing something globally that conflicts.

[apasov]

I also started getting this error after upgrading to v1.0.12
In my case there are two errors. In addition to Cannot read property 'block' of undefined I get Cannot read property 'render' of undefined:

Both are fixable by :no-container="true"

[SouthRibbleTech]

I can also confirm that :no-container="true" works. Thanks @apasov I have spent 2 hours thinking I was going senile.

[SouthRibbleTech]

I am noticing that some markdown is not working i.e. ::: this is not displayed as a block :::

[hawkeye64]

@apasov @SouthRibbleTech Can you upgrade to v1.0.13 and tell me if you are still getting the container issue?

[Lecraminos]

I can confirm the above issue and "fix" in a similar setting (Chrome 79 on Manjaro) and unfortunately the error persists even after upgrading to 1.0.13... Used to work in 1.0.11, but interestingly even a downgrade (including removal of lock-file and node_modules) does not solve the issue anymore... Might it be introduced by a dependency upgrade?

[apasov]

@SouthRibbleTech lol)
@hawkeye64 Yes, I had already upgraded to v1.0.13 when I was writing the previous comment. The issue appeared after upgrading from v1.0.11 to v1.0.12

[hawkeye64]

So, fixed with v1.0.13?

[apasov]

No, not fixed.

[hawkeye64]

@apasov @Lecraminos @mesqueeb I would appreciate it if you guys would install the latest and verify the latest (v1.0.15) put this issue to bed. Thanks. ❤️

[apasov]

I confirm. Works without :no-container="true"
Thanks!

[hawkeye64]

Perfect!

[mesqueeb]

@hawkeye64 sadly it didn't work for me. : (
I'm still getting the error.

[hawkeye64]

Yes, it's back. The fix breaks SSR, so had to revert it. To implement the fix yourselves, don't install the app-extension (unless you need *.md or *.vmd imports). Instead, install the @quasar/quasar-ui-qmarkdown component by itself. Then you have to write a boot file, and this is different than normal.

import Vue from 'vue'
import VuePlugin from '@quasar/quasar-ui-qmarkdown/src/index.js'
// normally the above line would be like this: import VuePlugin from '@quasar/quasar-ui-qmarkdown'

Vue.use(VuePlugin)

The problem lies within how the markdown-it plugins are created and imported. I have tried two different transpilers with rollup with different outcomes. I may have to implement babel, but really didn't want to. Or, make copies of all the plugins (maintenance nightmare) and write them properly for the transpiler.

[mesqueeb]

@hawkeye64 perhaps a great time to consider marked!
https://bundlephobia.com/[email protected]

It's 4 times smaller and is more popular on Github. 😉

[hawkeye64]

@mesqueeb Thanks, I'll take a look at it

[mesqueeb]

@hawkeye64 it couldn't find the library when I did

import QMarkdown from 'quasar-ui-qmarkdown/src/index.js'

But it did when I did this:

import QMarkdown from '@quasar/quasar-ui-qmarkdown/src/index.js'

just a heads up for the others 😉

[hawkeye64]

@mesqueeb Thanks. I updated my example. Note, I found doing it that way breaks SSR.

Currently, investigating other markdown providers, including writing my own with AST parser to get better performance. This may take some time to come up with the best solution, but want something that is very long-term and not a band-aid (plaster).

[hawkeye64]

@apasov @Lecraminos @mesqueeb Such a tough bug. I have figured it out and have a fix. Look forward to a future release after I finish the rest of my testing.

[hawkeye64]

Fixed (finally) in v1.0.20