bump to 7.80

[tj2904]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
positive-press	✅ Ready (Inspect)	Visit Preview	Nov 17, 2023 0:16am

[github-actions]

Test coverage report (Jest)

❌ An unexpected error occurred. For more details, check console

Error: The process '/usr/local/bin/npx' failed with exit code 1

St.❔	Category	Percentage	Covered / Total
🔴	Statements	56.39% (-6.02% 🔻)	75/133
🔴	Branches	41.67%	10/24
🔴	Functions	51.92% (-3.85% 🔻)	27/52
🔴	Lines	54.69% (-6.25% 🔻)	70/128

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🔴	layout.tsx	0% (-100% 🔻)	100%	0% (-100% 🔻)	0% (-100% 🔻)
🔴	... / analytics.tsx	0% (-100% 🔻)	100%	0% (-100% 🔻)	0% (-100% 🔻)

Test suite run failed

Failed tests: 0/20. Failed suites: 2/16.

  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • 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/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /home/runner/work/positive-press/positive-press/node_modules/@vercel/analytics/dist/react/index.js:4
    import { useEffect } from "react";
    ^^^^^^

    SyntaxError: Cannot use import statement outside a module



      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (app/components/analytics.tsx:181:27)
      at Object.<anonymous> (app/layout.tsx:220:26)
      at Object.<anonymous> (__tests__/RootLayout.test.tsx:9:54)

---

  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • 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/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /home/runner/work/positive-press/positive-press/node_modules/@vercel/analytics/dist/react/index.js:4
    import { useEffect } from "react";
    ^^^^^^

    SyntaxError: Cannot use import statement outside a module



      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (app/components/analytics.tsx:181:27)
      at Object.<anonymous> (__tests__/Analytics.test.tsx:9:20)

Report generated by 🧪jest coverage report action from 1a32b95