Error when attempting to run with showdown 1.3.0

[matatk]

Thanks for this helpful extension :-).

I'm using it with showdown 1.3.0 via grunt-showdown (actually via ferllings/grunt-showdown because the original repo doesn't work with showdown 1.3.0). When I try to use showdown-toc I get the following error:

Error in 2 extension-> sub-extension 0: property "type" must be a string, but undefined given

This does not appear to be grunt-showdown-specific because if I comment out showdown-toc it works fine; also I am using other showdown extensions such as showdownjs/prettify-extension.

I am using a config like this in Gruntfile.js:

        showdown: {
            all: {
                options: {
                    customExtensions: ['showdown-prettify', 'showdown-toc']
                },
                files: [{
                    expand: true,
                    src: 'tmp/book/**/*.md',
                    ext: '.html'
                }]
            }
        },

[JanLoebel]

Thanks, I will have a look at it as soon as I have time. Sorry for that!

Is there any chance that you can provide me a test-project to reproduce this error?

[matatk]

Sorry for the very slow reply. I am not terribly experienced with using Grunt and node yet, and I've not been able to come up with a minimal example. However, I was wondering... there is a note about showdown-toc requiring cheerio if it's running on Node in the README, but cheerio is not listed as a dependency in showdown-toc's package.json (it's only listed as a devDependency) -- might this be part of the issue? (I'm not convinced, but it's the only thing I could think of so far.)

I also read that showdown's extension mechanism is undergoing changes (showdownjs/showdown#224). However the code you have appears to specify a type key, just as showdown-footnote does (and I assume that code still works). And the error I'm getting is not that deprecation warning.

So at the moment I'm a bit stuck as to how to reproduce this, other than the above thoughts.

[lolmaus]

I've had the same issue in my custom Showdown addon. Works fine in a browser but crashes in Node.

The solution was to return a hash (not an array of hashes) from the callback passed into showdown.extension().

[JanLoebel]

Sorry for the very late response. Now I found time to have a look. I think @lolmaus is right, I changed returning only an object and not an array anymore. It would be cool if anybody could verify the fix :)