-
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
"nx add @nx/nuxt" leads to "NX Cannot read properties of undefined (reading 'split')" #28506
Comments
i tried to run |
i think it is related to #28374 and I also suspect it is related to #27736 because of the error message is also "Cannot read properties of undefined (reading 'split')". however. i tried to run command |
<!-- 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 --> We switched to using `loadConfigFile` from `@nx/devkit` to load Nuxt Config files when plugins were not isolated. However, they are now, so we can use `loadNuxtConfig` again. The effect of using `loadConfigFile` paired with Nuxt's auto-imports resulted in inconsistent failures. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> Use `loadNuxtConfig` when `NX_ISOLATE_PLUGINS=true` ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #28506 Fixes #28374
<!-- 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 --> We switched to using `loadConfigFile` from `@nx/devkit` to load Nuxt Config files when plugins were not isolated. However, they are now, so we can use `loadNuxtConfig` again. The effect of using `loadConfigFile` paired with Nuxt's auto-imports resulted in inconsistent failures. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> Use `loadNuxtConfig` when `NX_ISOLATE_PLUGINS=true` ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #28506 Fixes #28374 (cherry picked from commit be7bfa4)
<!-- 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 --> We switched to using `loadConfigFile` from `@nx/devkit` to load Nuxt Config files when plugins were not isolated. However, they are now, so we can use `loadNuxtConfig` again. The effect of using `loadConfigFile` paired with Nuxt's auto-imports resulted in inconsistent failures. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> Use `loadNuxtConfig` when `NX_ISOLATE_PLUGINS=true` ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #28506 Fixes #28374 (cherry picked from commit be7bfa4)
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Current Behavior
Me again, with the beloved "NX Cannot read properties of undefined (reading 'split')" error again.
This time when trying to add the nx/nuxt plugin
I've added my project's configurations, at least those that I believe are relevant.
Expected Behavior
Fail with a clear message that helps the user / add the plugin as expected
GitHub Repo
No response
Steps to Reproduce
root tsconfig.base.json
nx.json
.npmrc
Nx Report
NX Report complete - copy this into the issue template
Node : 22.9.0
OS : win32-x64
Native Target : x86_64-windows
pnpm : 9.12.1
nx : 20.0.1
@nx/js : 20.0.1
@nx/jest : 20.0.1
@nx/eslint : 20.0.1
@nx/workspace : 20.0.1
@nx/devkit : 20.0.1
@nx/esbuild : 20.0.1
@nx/eslint-plugin : 20.0.1
@nx/express : 20.0.1
@nx/node : 20.0.1
@nx/nuxt : 20.0.1
@nx/playwright : 20.0.1
@nx/vite : 20.0.1
@nx/vue : 20.0.1
@nx/web : 20.0.1
@nx/webpack : 20.0.1
typescript : 5.6.3
Registered Plugins:
@nx/vite/plugin
@nx/eslint/plugin
@nx/playwright/plugin
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: