17 Commits

Author SHA1 Message Date
Nicholas Cunningham
51bed0e456
feat(nextjs): add support for typescript Next.js config file (#28709)
<!-- Please make sure you have read the submission guidelines before
posting an PR -->
<!--
https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr
-->

<!-- Please make sure that your commit message follows our format -->
<!-- Example: `fix(nx): must begin with lowercase` -->

<!-- If this is a particularly complex change or feature addition, you
can request a dedicated Nx release for this pull request branch. Mention
someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they
will confirm if the PR warrants its own release for testing purposes,
and generate it for you if appropriate. -->

## Current Behavior
<!-- This is the behavior we have today -->

## Expected Behavior
<!-- This is the behavior we should expect with the changes in this PR
-->

## Related Issue(s)
<!-- Please link the issue being fixed so it gets closed when this is
merged. -->

Fixes #28572
2024-10-30 16:15:48 -04:00
James Garbutt
74061cf5ef
cleanup(nextjs): migrate to node FS (#28065) 2024-10-01 14:35:18 +04:00
Jack Hsu
4ab9e6dc14
fix(nextjs): fix inlined workspace root in .nx-helpers (#27136)
This PR fixes an issue where our `withNx` function for Next.js is
compiled with inlined `workspaceRoot` (to support container
environments). On Windows, we write the `.nx-helpers/with-nx.js` with
the following:

```js
workspaceRoot: 'C:\Users\user\projects\app',
```

The `\u` character result in a Node error: `Invalid Unicode escape
sequence`.

The fix is to escape `\` as `\\`, so when the file is written, the path
is valid and does not cause unicode errors.

<!-- If this is a particularly complex change or feature addition, you
can request a dedicated Nx release for this pull request branch. Mention
someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they
will confirm if the PR warrants its own release for testing purposes,
and generate it for you if appropriate. -->

## Current Behavior
<!-- This is the behavior we have today -->

## Expected Behavior
<!-- This is the behavior we should expect with the changes in this PR
-->

## Related Issue(s)
<!-- Please link the issue being fixed so it gets closed when this is
merged. -->

Fixes #18824
2024-07-25 18:01:27 -06:00
Jason Jean
a64a7e2db9
feat(core): cleanup for v19 (#22993) 2024-05-01 12:12:32 -04:00
Nicholas Cunningham
aa622bab5a fix(nextjs): src package.json should not be copied to output folder
closes: #21535
2024-02-08 09:44:47 +01:00
Nicholas Cunningham
b1bb89256c
fix(nextjs): read nextConfig path correctly when provided as an option. (#20241) 2023-11-14 11:01:24 -07:00
Nicholas Cunningham
3008be1e7a
fix(nextjs): Running nx build --configuration=development should not throw an error (#17866) 2023-06-29 21:18:50 -04:00
Nicholas Cunningham
a546d5f737
fix(nextjs): Support importing json files inside next.config.js (#17623) 2023-06-15 12:49:47 -06:00
Jack Hsu
9881efa4dc
feat(nextjs): remove the "root" option from Next.js build executor since it can be inferred (#17248) 2023-05-26 19:08:02 +00:00
Jack Hsu
45a01710aa
fix(nextjs): support config files with dots in filename (#17204) 2023-05-25 08:49:28 -06:00
Jack Hsu
b6361738a4
fix(nextjs): support relative imports in next.config.js (#17127) 2023-05-23 14:34:12 -04:00
Jack Hsu
564ffaeebd
fix(nextjs): remove the need to install @nx/next for production builds (#16469) 2023-04-21 16:13:16 -04:00
Jason Jean
2d195007b0
feat(core): switch packages to use the @nx scope (#16069) 2023-04-14 19:56:37 -04:00
Jack Hsu
c7e49c564a
fix(nextjs): produce correct next.config.js file for production server (#15824) 2023-03-22 14:03:09 -04:00
Miroslav Jonaš
ab6f62a9b5
feat(core): move runtime-lint-utils to eslint plugin (#13222) 2022-11-18 12:24:53 +01:00
Jack Hsu
50f6cbb11d
feat(nextjs): remove dependency on "@nrwl/next" for the production build (#12247) 2022-09-26 12:38:44 -04:00
Jason Jean
fd18b5edec
feat(react): migrate next builders to devkit (#4861) 2021-02-23 11:39:20 -05:00