-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError: Cannot read properties of undefined (reading 'split') #27736
Comments
This is the most annoying and verbose issue with Nx I've ever faced, because the sources can be several, but the information you get out of it is close to none |
This was referenced Nov 1, 2024
FrozenPandaz
pushed a commit
that referenced
this issue
Nov 6, 2024
…28761) <!-- 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 #27736 and #27736 (cherry picked from commit 906cc1a)
FrozenPandaz
pushed a commit
that referenced
this issue
Nov 12, 2024
…28761) <!-- 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 #27736 and #27736 (cherry picked from commit 906cc1a)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current Behavior
I try to build my package and get the error like this:
with verbose it looks like this:
Expected Behavior
I expect to see the real reason why my script has failed, but currently it fails just handling another errors
GitHub Repo
No response
Steps to Reproduce
I do not know how to reproduce, but there can be a chance when we have not an error, but an empty object in the following code contruction:
The error later happens in this code:
nx/packages/nx/src/project-graph/utils/project-configuration-utils.ts
Line 374 in 3cbe2ab
Nx Report
Failure Logs
No response
Package Manager Version
No response
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: