SFC page compile error

[psi-4ward]

• I confirm that this is a issue rather than a question.

Bug report

As far as I've seen SFCs are supported along md-Files for pages.

If I add any my-page.vue I'll get

TypeError: Cannot read property 'parseComponent' of undefined
    at Object.parse (node_modules/@vue/component-compiler-utils/dist/parse.js:14:23)
    at parse (node_modules/@vuepress/shared-utils/lib/parseVueFrontmatter.js:17:47)
    at Page.process (node_modules/@vuepress/core/lib/prepare/Page.js:125:30)

This is cause @vuepress/shared-utils/lib/parseVueFrontmatter.js gets transpiled to

    const output = component_compiler_utils_1.parse({
        source: src,
        compiler: vue_template_compiler_1.default,
        needMap: false
    });

see the wrong .default at compiler prop.
If I remove this it works as expected.
Another typescript gotcha?

Version

1.0.0-alpha.29

[ulivz]

To report an issue that only happens in the scene you are in, the best and direct way is to provide a reproduction repo (e.g. vuepress-issue-example), otherwise I don't know where you are going wrong.

[psi-4ward]

see https://github.com/psi-4ward/vuepress-issue-parseVueFrontmatter

$ npm i
$ npm run build


> [email protected] build vuepress-issue-example
> vuepress build archive

wait Extracting site metadata...
modulesPath: vuepress-issue-example/node_modules
tip Apply theme located at vuepress-issue-example/archive/.vuepress/theme...
[vuepress] cannot resolve plugin "vuepress-issue-example/archive/.vuepress/theme"
tip Apply plugin @vuepress/register-components (i.e. "@vuepress/plugin-register-components") ...
TypeError: Cannot read property 'parseComponent' of undefined
    at Object.parse (vuepress-issue-example/node_modules/@vue/component-compiler-utils/dist/parse.js:14:23)
    at parse (vuepress-issue-example/node_modules/@vuepress/shared-utils/lib/parseVueFrontmatter.js:16:47)
    at Page.process (vuepress-issue-example/node_modules/@vuepress/core/lib/prepare/Page.js:125:30)

[tonyxu-io]

I have the same issue, removing default solved the problem.