#950 Invalid pact file created after migration to pact v10: pact:matcher:type in response body Issue created by M-Landwehr Software versions • OS: Windows 10 • Consumer Pact library: pact-foundation/pact: 10.1.4, • Node Version: 16.17.0 Issue Checklist Please confirm the following: ☑︎ I have upgraded to the latest ☑︎ I have the read the FAQs in the Readme ☑︎ I have triple checked, that there are no unhandled promises in my code and have read the section on intermittent test failures ☑︎ I have set my log level to debug and attached a log file showing the complete request/response cycle ☑︎ For bonus points and virtual high fives, I have created a reproduceable git repository (see below) to illustrate the problem Expected behaviour Migration of consumer tests from pact 9 to pact 10 should be possible without major changes except the ones described in https://docs.pact.io/implementation_guides/javascript/docs/migrations/9-10. The created pact file should still be valid. Actual behaviour After the update from pact 9 to pact 10, the pact mock response is wrong: It contains properties like

'pact:matcher:type': 'type', min: 1

. A pact file is still created, but contains invalid responses. Steps to reproduce • clone https://github.com/M-Landwehr/poc/tree/pact-10-vs-pact-9 • run npm i and then npm t The created pact file looks like this:

"response": {
        "body": {
          "result": {
            "min": 1,
            "pact:matcher:type": "type",
            "value": [
              {
                "cancelled": {
                  "pact:matcher:type": "type",
                  "value": false
                },
                "complexObject": {
                  "pact:matcher:type": "type",
                  "value": {
                    "value": {
                      "pact:matcher:type": "type",
                      "value": "value"
                    }
                  }
                },
                "descriptions": {
                  "pact:matcher:type": "type",
                  "value": {
                    "en": {
                      "pact:matcher:type": "type",
                      "value": "foo"
                    }
                  }
                },
                "name": {
                  "pact:matcher:type": "type",
                  "value": "name"
                }
              }
            ]
          }
        },

This seems to be a regression in pact 10: After changing the version to

^9.0.0

in the package.json the pact file is valid. According to the logs, the issue seems to be with the header matcher:

2022-09-23T11:08:11.354110Z  WARN ThreadId(01) pact_models::content_types: Failed to parse '{"value":"application/json;charset=UTF-8","regex":"application/json(;\\s?charset=[\\w\\-]+)?","pact:matcher:type":"regex"}' as a content type: mime parse error: an invalid token was encountered, 7B at position 0
2022-09-23T11:08:11.354186Z  WARN ThreadId(01) pact_models::content_types: Failed to parse '{"value":"application/json;charset=UTF-8","regex":"application/json(;\\s?charset=[\\w\\-]+)?","pact:matcher:type":"regex"}' as a content type: mime parse error: an invalid token was encountered, 7B at position 0

removing the headers section from the willRespondWith part in the spec.js file and rerunning the test also results in a correct pact file Relevant log files log.log pact-foundation/pact-js