fix(nextjs): fix .babelrc for libraries

[puku0x]

Current Behavior

The .babelrc generated by nx g @nrwl/next:library does not use @nrwl/next/babel preset.

Expected Behavior

It should be generated with @nrwl/next/babel preset.

// Example of `nx g @nrwl/next:library --style=@emotion/styled`
{
  "presets": [
    [
      "@nrwl/next/babel",  // 👈 The preset should be changed from next/babel to @nrwl/next/babel
      {
        "preset-react": {
          "runtime": "automatic",
          "importSource": "@emotion/react"
        }
      }
    ]
  ],
  "plugins": ["@emotion/babel-plugin"]
}

Related Issue(s)

https://nrwlcommunity.slack.com/archives/C015WMB2A8P/p1639043467125800
https://nrwlcommunity.slack.com/archives/C015WMB2A8P/p1641384957180500
#6728

[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/nrwl/nx-dev/4guZpfexM8ynp18LekqM4YKsWVvy
✅ Preview: Canceled

[Deployment for 5d1c31c canceled]

[nx-cloud]

Nx Cloud Report

CI ran the following commands for commit 5d1c31c. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

Status	Command
	nx affected --target=e2e --base=d6307181abae9538f83224565907c7c99e3b9d6e --head=5d1c31c2445bdf9d366df6bf4a59d32ed6226563 --exclude=e2e-react-native,e2e-detox,e2e-gatsby --parallel=1
	nx run-many --target=build --all --parallel=8
	nx affected --target=test --base=d6307181abae9538f83224565907c7c99e3b9d6e --head=5d1c31c2445bdf9d366df6bf4a59d32ed6226563 --parallel --max-parallel=3
	nx affected --target=build --base=d6307181abae9538f83224565907c7c99e3b9d6e --head=5d1c31c2445bdf9d366df6bf4a59d32ed6226563 --parallel --max-parallel=3
	nx build typedoc-theme

---

Sent with 💌 from NxCloud.

[kirjai]

i forget why we switched away from @nrwl/next/babel in favor of next/babel other than aligning ourselves closer to the default Nextjs configuration. so to be honest, i'm a bit reluctant switching back, considering that this doesn't solve any issues, it'd be done just for consistency. That's if i understood the motivation behind this PR correctly. if not - please let me know!

@jaysoo do you happen to recall why we switched away from @nrwl/next/babel, perhaps?

[zanettin]

just a side note but this also fixes the issue that custom libraries are not able to be unit tested. with the published solution you'll get this error:

    import React from "react";
    ^^^^^^

    SyntaxError: Cannot use import statement outside a module

    > 1 | export * from './lib/testlib';

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.