fix: fail to test specific package

[billyyyyy3320]

Summary

yarn test will run every tests in all workspaces.

When I looked at the source code, I found that there's an option to test a specific package:

// scripts/test.js
if (args.p) {
  const packages = (args.p || args.package).split(',').join('|')
  regex = `.*@vuepress/(${packages}|plugin-(${packages}))/.*\\.spec\\.(js|ts)$`
  const i = rawArgs.indexOf('-p')
  rawArgs.splice(i, 2)
}

const jestRunner = createJestRunner([
  '--config', 'scripts/jest.config.js',
  '--runInBand',
  ...(regex ? [regex] : [])
], rawArgs)

But when I ran yarn test -p core, it failed with ReferenceError: core is not defined.

I tracked down createJestRunner and found it is caused by #1404.

The rawArgs is supposed to contain '--inspect-brk', but it will also contain'-p' and 'core' if I run yarn test --inspect-brk -p core :

// @test-utils/lib/createJestRunner.js
const execa = require('execa')
const rawArgs = process.argv.slice(2)

const usedPorts = []

module.exports = function createJestRunner (jestArgs) {
  return async function () {
    const execArgv = getChildProcesExecArgv()
    const args = [...execArgv, ...jestArgs]
    console.log(`running node with args: ${args.join(' ')}`)
    args.unshift(...rawArgs, require.resolve('jest-cli/bin/jest'))
    await execa('node', args, {
      stdio: 'inherit'
    })
  }
}

Since rawArgs has been processed properly in scripts/test.js:

  const i = rawArgs.indexOf('-p')
  rawArgs.splice(i, 2)

I add a argument - rawArgs to createJestRunner. It also make it a bit more reusable.

What kind of change does this PR introduce? (check at least one)

• Bugfix
• Feature
• Code style update
• Refactor
• Docs
• Build-related changes
• Other, please describe:

If changing the UI of default theme, please provide the before/after screenshot:

Does this PR introduce a breaking change? (check one)

• Yes
• No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

• When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)

You have tested in the following browsers: (Providing a detailed version will be better.)

• Chrome
• Firefox
• Safari
• Edge
• IE

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature
• Related documents have been updated
• Related tests have been updated

To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.

Other information:

[billyyyyy3320]

Edit because tests in shared-utils are .ts files.

[billyyyyy3320]

Later, I think the second arg of createJestRunner - rawArgs is kinda weird since it can only contain --inspect-brk. I change it into accepting a simple boolean: 6547f8e