Actually, it was working well before last week. From last week we had this issue.
After I dig into it, I found the exact issue which produces from your css-selector-tokenizer dependency.
You have been mentioned this dependency css-selector-tokenizer: ^0.7.0 with a cap symbol. They published the latest version 0.7.1 which was automatically updated because of the cap on it. That's why we got this issue. Please verify on your side and fix this issue.
It would be better to remove the cap symbol on every dependency you have used in your package. You can rely on your package If you do it.
`
● Test suite failed to run
SyntaxError: classAtom at position 12
((?:\.|[A-Za-z_-\u
at bail (../../../../packages/app/react-cli/node_modules/regjsparser/parser.js:1119:13)
at parseNonemptyClassRanges (../../../../packages/app/react-cli/node_modules/regjsparser/parser.js:1043:9)
at parseClassRanges (../../../../packages/app/react-cli/node_modules/regjsparser/parser.js:997:15)
at parseCharacterClass (../../../../packages/app/react-cli/node_modules/regjsparser/parser.js:979:15)
at parseAtom (../../../../packages/app/react-cli/node_modules/regjsparser/parser.js:643:22)
at parseTerm (../../../../packages/app/react-cli/node_modules/regjsparser/parser.js:484:18)
at parseAlternative (../../../../packages/app/react-cli/node_modules/regjsparser/parser.js:457:21)
at parseDisjunction (../../../../packages/app/react-cli/node_modules/regjsparser/parser.js:440:18)
at finishGroup (../../../../packages/app/react-cli/node_modules/regjsparser/parser.js:514:18)
at parseGroup (../../../../packages/app/react-cli/node_modules/regjsparser/parser.js:510:14)
at parseAtom (../../../../packages/app/react-cli/node_modules/regjsparser/parser.js:659:16)
at parseTerm (../../../../packages/app/react-cli/node_modules/regjsparser/parser.js:484:18)
at parseAlternative (../../../../packages/app/react-cli/node_modules/regjsparser/parser.js:457:21)
at parseDisjunction (../../../../packages/app/react-cli/node_modules/regjsparser/parser.js:437:16)
at finishGroup (../../../../packages/app/react-cli/node_modules/regjsparser/parser.js:514:18)
at parseGroup (../../../../packages/app/react-cli/node_modules/regjsparser/parser.js:510:14)
at parseAtom (../../../../packages/app/react-cli/node_modules/regjsparser/parser.js:659:16)
at parseTerm (../../../../packages/app/react-cli/node_modules/regjsparser/parser.js:484:18)
at parseAlternative (../../../../packages/app/react-cli/node_modules/regjsparser/parser.js:457:21)
at parseDisjunction (../../../../packages/app/react-cli/node_modules/regjsparser/parser.js:437:16)
at parse (../../../../packages/app/react-cli/node_modules/regjsparser/parser.js:1134:18)
at rewritePattern (../../../../packages/app/react-cli/node_modules/regexpu-core/rewrite-pattern.js:326:15)
at getSelectors (../../../../packages/app/react-cli/node_modules/css-selector-tokenizer/lib/parse.js:178:12)
at Object.<anonymous> (../../../../packages/app/react-cli/node_modules/css-selector-tokenizer/lib/parse.js:208:12)
at Object.<anonymous> (../../../../packages/app/react-cli/node_modules/css-selector-tokenizer/lib/index.js:1:106)
at Object.<anonymous> (../../../../packages/app/react-cli/node_modules/postcss-modules-resolve-imports/lib/resolvePaths.js:3:16)
at Object.<anonymous> (../../../../packages/app/react-cli/node_modules/postcss-modules-resolve-imports/lib/resolveDeps.js:16:17)
at Object.<anonymous> (../../../../packages/app/react-cli/node_modules/postcss-modules-resolve-imports/lib/sync.js:18:19)
at Object.<anonymous> (../../../../packages/app/react-cli/node_modules/postcss-modules-resolve-imports/index.js:3:18)
at Object.<anonymous> (../../../../packages/app/react-cli/node_modules/css-modules-require-hook/lib/index.js:29:22)
at Object.<anonymous> (../../../../packages/app/react-cli/lib/jest/setup.js:266:12)
Actually, it was working well before last week. From last week we had this issue.
After I dig into it, I found the exact issue which produces from your
css-selector-tokenizerdependency.You have been mentioned this dependency
css-selector-tokenizer: ^0.7.0with a cap symbol. They published the latest version 0.7.1 which was automatically updated because of the cap on it. That's why we got this issue. Please verify on your side and fix this issue.It would be better to remove the cap symbol on every dependency you have used in your package. You can rely on your package If you do it.
` ● Test suite failed to run
SyntaxError: classAtom at position 12 ((?:\.|[A-Za-z_-\u
`