Skip to content
This repository was archived by the owner on Feb 15, 2022. It is now read-only.

Bump next-transpile-modules from 4.1.0 to 6.2.0 #87

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Feb 4, 2021

Bumps next-transpile-modules from 4.1.0 to 6.2.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 [email protected])

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
  • 1d27170 6.2.0
  • 0708a24 Merge pull request #165 from martpie/temp-path-normalize
  • b68fbb8 Fix a small mistake in tests
  • 55c49ec Re-organize webpack matcher tests
  • 7153586 Fix createWebpackMatcher instantiation
  • 8e5504a Runs some tests conditionally
  • 11b3d72 Merge branch 'master' into temp-path-normalize
  • 5b69f31 Merge pull request #164 from martpie/various-things-2
  • 915bf81 Drop unstable_webpack5 / automatic Webpack 5 detection
  • 9aef9dd Optimize CI pipeline for PRs
  • Additional commits viewable in compare view

Dependabot compatibility score

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 dependabot bot added the dependencies Pull requests that update a dependency file label Feb 4, 2021
@vercel
Copy link

vercel bot commented Feb 4, 2021

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/solvuu/ocamlorg2/pcs53h8r0
✅ Preview: Failed

[Deployment for 7392e59 failed]

@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/next-transpile-modules-6.2.0 branch from f739dd6 to af5228b Compare February 4, 2021 13:02
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/next-transpile-modules-6.2.0 branch from af5228b to 0bd4f8f Compare February 4, 2021 13:07
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/next-transpile-modules-6.2.0 branch from 0bd4f8f to c18f4c3 Compare February 5, 2021 18:51
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/next-transpile-modules-6.2.0 branch from c18f4c3 to 7392e59 Compare February 5, 2021 18:53
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Feb 9, 2021

Superseded by #98.

@dependabot dependabot bot closed this Feb 9, 2021
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/next-transpile-modules-6.2.0 branch February 9, 2021 06:48
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants