Aziz Gazanchiyan

Please, we need this fixed, nobody likes security warnings in their builds

Jest might not know, but we can extend it with such feature using custom environment definition, right? ```javascript async handleTestEvent(event, state) { if (event.name === 'test_done' && event.test.errors.length){ // generate...

@jwalakom well, you can zip your attachments and download them using PowerShell task in your pipeline, and then publish them wherever you want. You can't attach your logs per test...

@mmarkelov can we have this feature implemented please?

How about new `all` chainable? Something like `expect(page).all.toHaveText(selector, text, options)`?

well, it's something like this ``` project/ |_sources/ |_... |_webpack/ |_app/ |_webpack.base.config.js |_webpack.dev.config.js |_webpack.config.js |_postcss.config.js |_package.json ```

1. I run it using npm script `"watch:app": "nodemon --watch ../../.env --exec webpack",` 2. Yes - I do use `webpack-merge` 3. I have my `postcss-loader` defined in the `webpack.dev.config.js`, which...

Well, it is extremely strange, but if I try to create a new, simpler repo - I cannot reproduce this issue either. I'll try to investigate it further. P.S. It...

Well, I hope I won't be fired for sharing this :) It seems that not ALL accesses to `postcss.config` are failing, but only SOME of them. I also compile some...

OK, I think I've found the issue. So, once again - I have a monorepo, with packages. All package dependencies are hoisted to the root. Every package has it's own...