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

[dependabot]

Bumps next-transpile-modules from 4.1.0 to 6.3.0.

Release notes

Sourced from next-transpile-modules's releases.

6.2.0

• Fixed some issues with nested node_modules
• Fixed scoped packages transpilation on Windows
• Fixed Webpack 5 with Next.js 10.0.6
• Update tested Next.js version to 10.0.6

⚠ Webpack 5 users 👇

• unstable_webpack5 has been removed, please use future: { webpack5: true } in your next.config.js instead (requires next@10.0.6)

6.1.0

• Added support for module field in package.json
• Improved do not transpile nested node_modules (node_modules in node_modules)
• Improved dependencies hell (less dependencies when installing the plugin)
• Improved some FAQ points

6.0.0

Hello there 👋

shortly after the release of v5, here's v6, which solves some edgecases when transpiling modules. Again, no API changes, I still consider it major version as your build might break with this release.

The breaking changes are indicated by the ⚠️ icon.

Coming from v4? -> Please read the changes of v5 first ;)

⚠️ Fixed resolution strategy for packages resolving their main field to a sub-directory

Let's say a module/package is as follows:

styleguide/
    components/
    utils/ 
    package.json # <- `main` field resolving to components/index.js 

with v5, then only styleguide/components would get transpiled, and styleguide/utils/ would get ignored.

In v6, the behavior is similar to v4: everything in styleguide will get transpiled: components/ and utils/.

We lose granularity, but we get a much better DX out-of-the-box, and it matches the behavior of v4. This should solve most of the issues that you may have faced with v5.

Thanks to everyone who helped me test this 🙌

cheers!

5.0.0

Hello there, next-transpile-modules@5 is here! There are no API changes, but some internal changes introduced breaking behavioral changes.

Make sure you understand the changes before upgrading!

... (truncated)

Commits

• See full diff 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/lcjmlk3go
✅ Preview: https://split-interfac-git-dependabot-npmandyarninterfacenext-tr-c39cc8.split-fi.vercel.app

[dependabot]

Superseded by #123.