Nx compatibility

[osnoser1]

Is your feature request related to a problem? Please describe.
I'm trying to deploy an angular app with ssr using nx and netlify and I get an error because it doesn't find the angular.json file, and that is because the file was renamed to project.json file.

Describe the solution you'd like
Allow to specify the angular.json name or try to find a project.json file.

Additional context

• I'm trying to deploy this project: https://app.netlify.com/sites/limitless-angular-sanity-example/overview
• Error

Plugin "@netlify/angular-runtime" failed                      
9:19:03 PM: ────────────────────────────────────────────────────────────────
9:19:03 PM: ​
9:19:03 PM:   Error message
9:19:03 PM:   Error: Could not locate your angular.json at your project root or two levels above your publish directory. Make sure your publish directory is set to "{PATH_TO_YOUR_SITE}/dist/{YOUR_PROJECT_NAME}/browser", where {YOUR_PROJECT_NAME} is 'defaultProject' in your angular.json.
9:19:03 PM: ​
9:19:03 PM:   Plugin details
9:19:03 PM:   Package:        @netlify/angular-runtime
9:19:03 PM:   Version:        2.1.0
9:19:03 PM:   Repository:     git+https://github.com/netlify/angular-runtime.git
9:19:03 PM:   npm link:       https://www.npmjs.com/package/@netlify/angular-runtime
9:19:03 PM:   Report issues:  https://github.com/netlify/angular-runtime/issues
9:19:03 PM: ​
9:19:03 PM:   Error location
9:19:03 PM:   In "onPreBuild" event in "@netlify/angular-runtime" from Netlify app
9:19:03 PM: ​
9:19:03 PM:   Resolved config
9:19:03 PM:   build:
9:19:03 PM:     command: nx run sanity-example:build
9:19:03 PM:     commandOrigin: ui
9:19:03 PM:     publish: /opt/build/repo/dist/apps/sanity-example
9:19:03 PM:     publishOrigin: ui
9:19:03 PM:   plugins:
9:19:03 PM:     - inputs: {}
9:19:03 PM:       origin: ui
9:19:03 PM:       package: '@netlify/angular-runtime'
9:19:03 PM: Build failed due to a user error: Build script returned non-zero exit code: 2
9:19:04 PM: Failed during stage 'building site': Build script returned non-zero exit code: 2 (https://ntl.fyi/exit-code-2)
9:19:04 PM: Failing build: Failed to build site

[macgors]

+1
IMO this should be supported.

@osnoser1 Could I ask you how did you overcome this issue?

[osnoser1]

+1 IMO this should be supported.

@osnoser1 Could I ask you how did you overcome this issue?

Hi @macgors, I applied a patch here to be able to deploy with nx: https://github.com/limitless-angular/limitless-angular/blob/main/patches/%40netlify__angular-runtime.patch

[gwesterman]

I recently encountered the same issue. Netlify automatically detects an Angular application and sets the deploy runtime to Angular, enabling the @netlify/angular-runtime plugin. However, this plugin is not compatible with Nx.

The solution is straightforward:

1. Navigate to Site configuration → Build & deploy → Build settings, then click Configure
2. At the top, you will likely see Runtime: Angular and a Remove button
3. Click Remove, then save the updated configuration

This hands back control over the build to you, the developer.

Below are the settings I am using:

Base directory: [empty] (appears as / after saving)
Package directory: apps/my-app
Build command: nx run my-app:build:production
Publish directory: dist/apps/my-app/browser

[Cephyric-gh]

After figuring out a work around in 1 of our projects (I wrote a rough script that loops through every project.json that exists in the workspace and output an angular.json with them), I realised that there wasn't too much blocking NX from being supported by the runtime. Took a stab at it in #263.

As mentioned in the PR, it would be a cleaner DX/integration if packagePath was exposed to the runtime, as it currently has to enforce that the ANGULAR_PROJECT environment variable is set to the name of the project being deployed so it can build correct paths to the appropriate project.json, and assume the folder structure is unchanged from the default NX setup.

Very interested to hear thoughts!

[pieh]

Thanks to @Cephyric-gh contribution - this should be now fixed in the 2.3.0 release ( https://github.com/netlify/angular-runtime/releases/tag/v2.3.0 )