Closed dbigintonpro closed 4 years ago
Your stack trace shows that the source of your problem is within Angular's compiler extractCommentsWithHash.
We can also see from your wallaby configuration that you are using a null-loader for your styles. Our assumption is that this is what is causing your tests to fail. Could you please try updating your configuration to use a loader for your styles?
wallaby.js
module.exports = function(wallaby) {
...
return {
...
postprocessor: wallabyWebpack({
...
module: {
rules: [
...
{
test: /\.scss$|\.sass$/,
- // loaders: [{ loader: 'raw-loader' }, { loader: 'sass-loader', options: { implementation: require('sass') } }]
- loaders: ['null-loader'],
+ loaders: [{ loader: 'raw-loader' }, { loader: 'sass-loader', options: { implementation: require('sass') } }]
+ // loaders: ['null-loader'],
},
...
]
...
},
...
}),
...
};
};
I'm going to close this issue, as above, we assume the loader was the cause of the problem. If you're still having issues, please let us know and we'll re-open the issue.
Using Wallaby in our monorepo Nx environment provides a series of output errors that appear to be related to the loading of the tested. Running the tests via Karma, 99% pass.
Please note we are using Nx with Karma for the majority of our applications, but have a couple of nest apps using Jest. It is understood that we would need a separate config file for Jest (which we are not concerned with at this moment in time) but want to get the bulk of our tests working with Wallaby and Karam, hence our manual config file.
Wallaby diagnostics report