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

[dependabot]

Bumps next-transpile-modules from 4.1.0 to 7.2.0.

Release notes

Sourced from next-transpile-modules's releases.

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']);

...and everything will work fine.

7.0.0

Bonsoir! 👋 Following the release of Next.js 10.2, next-transpile-modules@7 is here!

v6 works perfectly with next@10.2.0, v7 only introduces an option default value change.

The breaking changes are indicated by the ⚠️ icon.

⚠️ resolveSymlinks: true by default

If you are using yarn/npm workspaces, it should not change anything, but compilation time and reloads will be faster.

If you are using npm/yarn link or npm's file:, you will need to set the option to false if you get compilation errors.

Webpack 5 support

Webpack 5 support is not experimental anymore! It will be disabled by default though, because this plugin updates the Next.js Webpack configuration. So if you want to use Webpack 5 (and enjoy all the bundles/compilation improvements), you'll need to explicitly enable it in your config:

... (truncated)

Commits

• 2d9de2c 7.2.0
• 926f8c5 Update quickie script
• 6046f02 Merge pull request #210 from fabianishere/global-css
• 8fadc6a Fix global SASS import tests
• 4e3c91f Allow Global CSS imports in modules outside node_modules
• 3726e70 Add support for global CSS imports
• d1f694b 7.1.2
• 5a5c40d Merge pull request #209 from martpie/fix-deprecation-warnings
• 5ea7f34 Remove unwanted change to webpack 4 test next.config.js
• 3526b55 Fix false-positive deprecation warnings
• 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/E4hkmj3Lrty7MG5VPQUx4k5a7dPd
✅ Preview: https://split-interfac-git-dependabot-npmandyarninterfacenext-tr-cf460f.vercel.app

[dependabot]

Superseded by #155.