build(deps): bump next-transpile-modules from 5.0.0 to 6.0.0

[dependabot]

Bumps next-transpile-modules from 5.0.0 to 6.0.0.

Release notes

Sourced from next-transpile-modules's releases.

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? -> then you can just upgrade to v6 directly (while still reading the changes of v5), this fix should not concern you. ;)

⚠️ 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!

Commits

• 59dc451 6.0.0
• 29fca16 Merge pull request #141 from martpie/resolve-modules-to-their-root-package-json
• ca913a0 Update compatibility table
• 61c1e7d Naming consistency improvements
• cc78e39 Update notes
• 7c586c8 Resolve modules to the directory of their package.json (instead of their dirn...
• 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

[mrtnzlml]

@michalsanger Why is the murmur hash needed here? 🤔

[michalsanger]

As I understand this, during a build within a monorepo, @adeira packages are not transpiled and we have to explicitly list them here. The murmur-hash is used in sx that's how it gets into build.

[mrtnzlml]

Ay caramba. So it's a dependency of a dependency. That's what I was afraid of. 🙈

I'd argue that this package (next-transpile-modules) no longer serves the purpose we were using it for. You have to be explicit like this since version 5 but what we really want to do is to transpile the @adeira/* scope and that's it (without enumerating every possible and even deeply nested workspace 🤦).

I will talk with the authors and see if we should fork it or what. Thanks!

[mrtnzlml]

Asked here: martpie/next-transpile-modules#143

[tbergquist-godaddy]

We should be able to get this programmatically using yarn workspaces info and grabbing all dependencies and nested dependencies.

[gaurav5430]

did you find an alternate package / solution for this ?

[tbergquist-godaddy]

Since we are transpiling workspaces from this monorepo, we decided to fetch it programmatically using the yarn workspaces info command, you can see the PR (here)[https://github.com//pull/1462]