The problem is that Jest is hitting these CSS imports and trying to parse them as if they were JavaScript.
The "Unexpected token ." message probably comes because the first line of the file it is choking on is a CSS class declaration, i.e. .datepicker: { ... }
.
Anyway, as pointed out in this answer, the way to get around this is to create a file containing a module which exports an empty object. I called mine styleMock.js
.
module.exports = {};
Then, you need to create a jest.config.js
file in your project root and add:
module.exports = {
moduleNameMapper: {
'\.(css|less)$': '<rootDir>/test/jest/__mocks__/styleMock.js',
}
};
The moduleNameMapper
setting tells Jest how to interpret files with different extensions. In this case we simply need to point it at the empty file we just created. Obviously adjust the path to your file accordingly.
And note that you can expand the regex above for whichever file endings you need. Mine looks like:
moduleNameMapper: {
'\.(jpg|jpeg|png|gif|eot|otf|webp|svg|ttf|woff|woff2|mp4|webm|wav|mp3|m4a|aac|oga)$':
'<rootDir>/test/jest/__mocks__/fileMock.js',
'\.(css|less)$': '<rootDir>/test/jest/__mocks__/styleMock.js',
},
where fileMock.js
is identical to styleMock.js
Alternatively, you could use a module such as jest-transform-stub, which does the same thing for you.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…