Bump next-transpile-modules from 4.1.0 to 8.0.0 in /interface

[dependabot]

Bumps next-transpile-modules from 4.1.0 to 8.0.0.

Release notes

Sourced from next-transpile-modules's releases.

8.0.0

Following the Next.js 11 announcement, next-transpile-modules v8 is here. Technically v7 should work fine, but there was a default change, so I mark this as a major version.

The breaking changes are indicated by the ⚠️ icon.

Webpack 5 enabled by default ⚠️

If you don't have any webpack5 key in your next.config.js, next-transpile-modules will assume you use Webpack 5.

If you already have Webpack 5 enabled, nothing changes for you. If you want to stick with Webpack 4, you can see how to disable Webpack 5 here.

It is of course strongly recommended to upgrade to Webpack 5, as it brings substantial improvements to compilation time!

next-transpile-modules will keep supporting Webpack 4 as long as Next.js does, and we'll gladly kill it with fire when Next.js won't support it no more :)

Cheers!

7.3.0

• Added support for top-level webpack5 configuration (next@canary)

7.2.0

• Added support for Global CSS imports from modules located in node_modules (thank you @​fabianishere!)

7.1.2

• Fixed false-positive deprecation warnings on Webpack 4 setups

7.1.1

• Fixed new package lookup for packages using exports field
• Fixed code that should have not been shipped yet

7.1.0

• Added new package lookup resolution
• Deprecated specific package file lookup

When trying to locate the packages you are trying to transpile, since v5, next-transpile-modules tries to resolve your module names you pass to it, which required a valid main or exports field. It will now tries to resolve directly to its package.json.

This should solve the issue for some people who did not want to use the main/exports fields for their local packages, and some others who wanted to use local packages locally while publishing them on NPM as well.

If next-transpile-modules cannot find your package package.json, it will fallback to the previous lookup system (a deprecation warning was added), so no breaking change is expected.

Basically, for the few that were using something like:

const withTM = require('next-transpile-modules')(['some/very/specific/file.js']);

You should now be able to use:

const withTM = require('next-transpile-modules')(['some']);
</tr></table> 

... (truncated)

Commits

• 6692f2f 8.0.0
• b1ce403 Merge pull request #218 from martpie/next-11
• 0c1b405 Tests: update TS and disable ESLint
• 3c2b14b Re-generate lockfiles with npm@6 + update actions
• 3e730c3 Use ubuntu-latest instead of ubuntu-18.04
• f133936 Add npm version script to CI
• 0c9d989 Re-generate npm-basic lockfile
• 429d8f8 Rollback all deps updates
• 2605d1d Rollback fs-extra
• 641f63d Re-update all dependencies
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/split-fi/split-interface/85zjDvsmPppQxxBWRGM3ycfTw3Zr
✅ Preview: https://split-interface-git-dependabot-npmandyarninterf-d065aa-split-fi.vercel.app

[dependabot]

Superseded by #220.