Skip to content

React Pact example - Need library to be updated #11

Open
@reachbharathan

Description

@reachbharathan

Current package.json has 78 vulnerabilities (65 low, 1 moderate, 12 high)
run npm audit fix to fix them, or npm audit for details

Need to update the below packages
apollo-cache-inmemory ^1.3.9 → ^1.6.3
apollo-client ^2.4.5 → ^2.6.4
apollo-link-http ^1.5.5 → ^1.5.16
axios 0.18.0 → 0.19.0
graphql ^14.0.2 → ^14.5.8
graphql-tag ^2.10.0 → ^2.10.1
node-fetch ^2.2.1 → ^2.6.0
react ^16.5.2 → ^16.10.1
react-dom ^16.5.2 → ^16.10.1
react-scripts 2.0.5 → 3.1.2
@pact-foundation/pact 7.0.3 → 9.1.1
@pact-foundation/pact-node 6.20.0 → 9.0.4
cross-env ^5.2.0 → ^6.0.0

Currently there are FAIL src/rest/hero.service.test.pact.js
● Test suite failed to run

Jest encountered an unexpected token

This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.

By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".

Here's what you can do:
 • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
 • If you need a custom transformation specify a "transform" option in your config.
 • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

You'll find more details and examples of these config options in the docs:
https://jestjs.io/docs/en/configuration.html

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions