[Bug report] 1.0.0-alpha.40 breaks #1204, #1206

[meteorlxy]

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

Bug report

Version

1.0.0-alpha.40

Steps to reproduce

d16d3d5#diff-56a897e96a354a8b8ea86dc24074ad5bR61

    const pkgPath = require.resolve(name)
    let packageRootDir = parse(pkgPath).dir
    // For those cases that "main" field was set to non-index file
    // e.g. `layouts/Layout.vue`
    while (!fs.existsSync(`${packageRootDir}/package.json`)) {
      packageRootDir = resolve(packageRootDir, '..')
    }

What is expected?

Allow "main" field to be set to something like lib/index.js (As explained in #1204 )

In such case, the packageRootDir should be <pkgDir>/lib/

What is actually happening?

The packageRootDir is <pkgDir> now.

[ulivz]

There is another more important case for now, a 0.x user would want to migrate his/her theme to 1.x and doesn't have themeEntry, so he need set the "main" field to layouts/Layout.vue. so we need to retrieve the correct theme path.

For your case you can try:

module.exports = {
   theme: require.resolve('vuepres-theme-xxx/lib')
}

[meteorlxy]

@ulivz

Emmm.. As I remembered, 0.x theme does not allow users to set the "main" field to layouts/Layout.vue

vuepress/lib/prepare/resolveOptions.js

Line 61 in a30f6fa

themeLayoutPath = require.resolve(`vuepress-theme-${siteConfig.theme}/Layout.vue`, {