v3.ocaml.org-rescript
v3.ocaml.org-rescript copied to clipboard
Update dependency next-transpile-modules to v9
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| next-transpile-modules | ^8.0.0 -> 9.0.0 |
Release Notes
martpie/next-transpile-modules
v9.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'
]);
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, click this checkbox.
This PR has been generated by WhiteSource Renovate. View repository job log here.