Andreas Lind

Support PostCSS insertBefore

2

- Webpack Version: n/a - Operating System (or Browser): Ubuntu Linux 18.04 - Node Version: 10.15.1 - postcss-values-parser Version: 3.0.1 ### How Do We Reproduce? ```js const postcssValuesParser = require('postcss-values-parser');...

1.x: HTML comment delimiters inside <script> ends the tag

1

``` var rawHtml = 'document.write("");', htmlparser = require('./lib/htmlparser'), handler = new htmlparser.DefaultHandler(), parser = new htmlparser.Parser(handler); parser.parseComplete(rawHtml); console.warn(require('util').inspect(handler.dom, false, null)); ``` Output: ``` [ { raw: 'script', data: 'script', type:...

1.x: Less thans and greater thans in attributes break the parser

2

Based on the example in http://www.whatwg.org/specs/web-apps/current-work/#attr-iframe-srcdoc : ``` var rawHtml = '', htmlparser = require('./lib/htmlparser'), handler = new htmlparser.DefaultHandler(), parser = new htmlparser.Parser(handler); parser.parseComplete(rawHtml); console.warn(require('util').inspect(handler.dom, false, null)); ``` Output: ```...

Expose connect options and the client socket via a _mitm property

6

Fixes #14. I ran into a scenario where it was impossible to pair up client sockets, connect options, and HTTP requests using the current API. This (or something similar) makes...

I ran into a problem in `unexpected-mitm`-land where a test would break when keep-alive is active. When connecting to the same host:port as a previous test had also touched, the...

Make connect opts available to request listeners

2

I'm implementing a "recording" mode in my testing lib where it would be really useful to know the originally intended host/port/etc. of the intercepted connection, which were passed as the...

Attribute selector with pipe gets mangled

1

Context: https://github.com/cssnano/cssnano/pull/925 ```js console.log(require('postcss-selector-parser')().processSync('[ foo | bar ]')); '[ foo ]' ``` Expected output: `[ foo | bar ]`. Interestingly, it does work when removing some of the whitespace around...

Remove the 'was [always] called with [exactly]' assertion

21

See #29. - [x] deprecate `was called with` in the docs - [x] deprecate `was called with` with `console.warn` - [ ] wait a while so users have had the...

I once did something like this: ``` js var spy1 = sinon.spy().named('spy1'); spy1(123); var spy2 = sinon.spy().named('spy2'); expect([spy1], 'to have calls satisfying', function () { spy1(123); spy2(456); }); ``` ......

Changes to the valueAccessor for the foreach binding aren't picked up

7

In my app I have a view where the `foreach` binding is used with an observable array that's replaced when the user navigates somewhere else. Something like this: ``` html...