Bump next-transpile-modules from 7.3.0 to 9.1.0

[dependabot]

Bumps next-transpile-modules from 7.3.0 to 9.1.0.

Release notes

Sourced from next-transpile-modules's releases.

9.1.0

• Add TS typings to the plugin (for better autocomplete), thanks @​belgattitude!
• Internal dependencies update

9.0.0

Chop chop! Next.js 12 yesterday, next-transpile-modules@9 today :] As always the breaking changes are indicated by the ⚠️ icon.

If you appreciate my work, and if you can afford it, you (or better, your company) can show support by sponsoring me (or just buying me a beer 🙌).

Support for Next.js 12

Nothing much to say. You should definitely upgrade, that's an amazing release!

Removed support for Webpack 4 ⚠️

What it says, next-transpile-modules is aligned with Next.js releases, so no more Webpack 4.

Removed support for legacy module resolution ⚠️

If you have seen in your logs with v8 the following warning:

DEPRECATED - fallbacking to previous module resolution system for module "XXX", you can now just pass the name of the package to transpile and it will detect its real path without you having to pass a sub-module.

this is for you.

You can read the 7.1.0 version changelog for a detailed explanation, but basically, what you want to do now is the following:

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

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 :)

... (truncated)

Commits

• d3b0025 Check typings on CI + linting/formatting earlier
• 8c24ed0 Update deps (#276)
• d6bc806 9.1.0
• be07e8c Merge pull request #274 from belgattitude/imrov-typings
• 60abe2f feat(typings): allow to preserve config type
• 0d44363 Update bug_report.md
• 770eab4 Update README.md
• 78b0a63 Merge pull request #262 from martpie/next-12.1.x
• d0f4047 Test Next.js 12.1.6 version
• f698944 Run tests on Node.js 14/16 instead of 12/14
• 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)

[dependabot]

Superseded by #80.