Pattern mode usage doesn't autocomplete spec test file routes

[dortamiguel]

🐛 Bug Report

When I'm in "Pattern Mode Usage" while running jest with "jest --watch" if I type a valid name for an .spec files the route doesn't gets autocompleted below the line "pattern >"

Maybe is related with my .jestconfig?

const jestConfig = {
	moduleFileExtensions: ['ts', 'tsx', 'js'],
	globals: {
		'ts-jest': {
			useBabelrc: true,
		},
	},
	transform: {
		'^.+\\.tsx?$': 'ts-jest',
		'^.+\\.jsx?$': 'babel-jest',
	},
	moduleNameMapper: {
		'.+\\.(css|styl|less|sass|scss|png|jpg|ttf|woff|woff2)$':
			'identity-obj-proxy',
	},
	testRegex: '(/__tests__/.*|(\\.|/)(test|spec))\\.(jsx?|tsx?)$',
	coveragePathIgnorePatterns: ['.*\\.d\\.ts', '<rootDir>/node_modules/'],
}

if (process.env.COVERAGE === 'all') {
	jestConfig.collectCoverageFrom = ['src/**/*.js', 'src/**/*.ts']
}

module.exports = jestConfig

[dortamiguel]

I have more info.

If I run

jest --watch

and then press p the option called "Press p to filter by a filename regex pattern."

I get this screen

The thing is that while I type I don't get any file path suggestion, but when I press enter the regex filter gets applied. As you can see in this screenshot

There is something wrong with my config. I read the docs a dozen of times and tried loads of different example config files. I'm missing something?

[mikehdt]

IIRC there was some license-type issues around the typeahead (autocomplete) stuff. It seems this may be what you're after:
https://github.com/jest-community/jest-watch-typeahead

If indeed that's the case, it would be good if the Jest documentation helped point towards it 😃

(Further discussion can be found here: #4931 )

[rickhanlonii]

Yeah @mikehdt is right - you'll need the plugin for typeahead

Happy to merge a docs PR that mentions it, but closing this as not a bug

[dortamiguel]

Thank you 🙂

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.