`ProjectsWithNoNameError` error after updating to v19 about nx

[jogelin]

Same issue here. I didn't investigate why exactly but it is related to:

• Upgrade to Nx 19
• Plugin inference activated
• Windows environments only
• Server app only

[guillempuche]

Similar when running my main Expo app. Tested in Nx 19 macos

Storybook is in its own standalone React Native app. Storybook packages v7.6.10 and v7.6.15 for @storybook/react-native.

Nx docs https://nx.dev/recipes/storybook/custom-builder-configs#and are outdated, framework field doesn't exist in StorybookConfig.

yarn exec nx run expo:start
node:internal/process/promises:289
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[Failed to process project graph. Run "nx reset" to fix this. Please report the issue if you keep seeing it.
  The "@nx/storybook/plugin" plugin threw an error while creating nodes from apps/storybook-rn/.storybook/main.ts:
    TypeError: Cannot read properties of undefined (reading 'name')
        at getStorybookFramework (/Users/guillem/programacio/codi/cites/nx-expo-next-tamagui/node_modules/@nx/storybook/src/plugins/plugin.js:170:66)
        at buildStorybookTargets (/Users/guillem/programacio/codi/cites/nx-expo-next-tamagui/node_modules/@nx/storybook/src/plugins/plugin.js:68:32)
        at Array.exports.createNodes (/Users/guillem/programacio/codi/cites/nx-expo-next-tamagui/node_modules/@nx/storybook/src/plugins/plugin.js:53:32)
        at /Users/guillem/programacio/codi/cites/nx-expo-next-tamagui/node_modules/nx/src/project-graph/plugins/utils.js:49:27
        at async Promise.all (index 0)

[jogelin]

I fixed my problem.

My error was a bit different:

Failed to process project graph. Run "nx reset" to fix this. Please report the issue if you keep seeing it.
  ProjectsWithNoNameError: The projects in the following directories have no name provided:
    - apps\my-app-one
    - apps\my-app-two
    - apps\my-app-three
    - ...

All of the apps above were related to a specific Nx plugin using target inference.

Nx can inject targets into a project configuration by comparing the projectRoot computed with the projectRoot from the list of existing projects .
However, the projectRoot computed can be different between a Windows environment and a Unix environment.

This is why Nx created the utility normalizePath to avoid that use case:

const projectRoot = normalizePath(join(dirname(configFilePath), '..'));

[FrankFan]

blocked by the same issue: The projects in the following directories have no name provided: in Mac

how to solve this ?

[FrankFan]

blocked by the same issue: The projects in the following directories have no name provided: in Mac

how to solve this ?

answer

in nx apps/folder, a react project's there is a lib sub-folder in public folder , but it's package.json file has no name filed , this is the root cause.

[KranzAklilu]

Make sure your project.json has something inside {"name": ' "} and run nx reset