rowens72
commented
1 month ago I'm running into this same issue.
Open abmprottoy opened 1 month ago
rowens72
commented
1 month ago I'm running into this same issue.
pdannell
commented
1 month ago I think they corrected this but added a new bug, or the VS installer isn't doing something correctly.
When I am generating a new ASP.NET with React(Typescript) project, the node version in the package.json shows up as ^20.16.0 which reflects the version my console spits out when using node -v.
However, if you delete the ^20.16.0 and check the latest version that auto-populates it only goes up to 20.14.13. This compiles fine when used it looks like.
@rowens72, if you want to confirm that the original posters fix worked, or you had to set it to 20.14.13?
soolafsen
commented
1 day ago This is still an issue. Manually setting node as described above works.
Is there an existing issue for this?
Describe the bug
Error description suggests it's something with npm install. This is an area where error reporting could be improved and could be provided the actual error from npm but that's topic for another issue.
So, I opened up the terminal and cd'd into the front-end react folder (
projectname.client) to do a manual npm install. Here's the output from npm now:Looks like we found our error. It's apparently the
@types/node@^22.4.0package. Might be a caching issue on local machine? But first let's check npmjs to see if the package actually exists! From npmjs, it seems the package actually exists and as of writing this the latest version is20.14.10which was published 4 days ago. In its current history of 1,849 versions published there is no existence of version 22.4.0 in the package registry.So where did this 22.4.0 came from?
If you use latest nodejs on your machine you're probably familiar with this version number. It's the version of your NodeJS. .NET 8 came out recently and on best guess, this might be an erroneous update of the
package.jsonwhere it was thought the latest node version would also be the latest version for an external package. If we take a peek into thepackage.jsonfile, we'll even see this package was added at the very last. Coherence would have kept it together with other @types/packages. You may take a look here:package.json
{ "name": "reactapptrial.client", "private": true, "version": "0.0.0", "type": "module", "scripts": { "dev": "vite", "build": "tsc -b && vite build", "lint": "eslint . --ext ts,tsx --report-unused-disable-directives --max-warnings 0", "preview": "vite preview" }, "dependencies": { "react": "^18.3.1", "react-dom": "^18.3.1" }, "devDependencies": { "@types/react": "^18.3.3", "@types/react-dom": "^18.3.0", "@typescript-eslint/eslint-plugin": "^7.13.1", "@typescript-eslint/parser": "^7.13.1", "@vitejs/plugin-react": "^4.3.1", "eslint": "^8.57.0", "eslint-plugin-react-hooks": "^4.6.2", "eslint-plugin-react-refresh": "^0.4.7", "typescript": "^5.2.2", "vite": "^5.3.1", "@types/node": "^22.4.0" } }To test my assumption, I then updated the version number to current available version on npmjs. And to my surprise, the project now runs without any error. Hence proved, the bug is in the version number of this package.
Expected Behavior
The expected behavior is of course, pressing F5 on an unmodified project template to run successfully without any errors.
Steps To Reproduce
The steps to reproduce this issue are very simple and you don't even need additional code samples from us either.
Exceptions (if any)
Currently None.
.NET Version
8.0.302
Anything else?
dotnet --info.NET SDK: Version: 8.0.302 Commit: ef14e02af8 Workload version: 8.0.300-manifests.ca8b4b2d MSBuild version: 17.10.4+10fbfbf2e Runtime Environment: OS Name: Windows OS Version: 10.0.22631 OS Platform: Windows RID: win-x64 Base Path: C:\Program Files\dotnet\sdk\8.0.302\ .NET workloads installed: [maui-windows] Installation Source: VS 17.10.35013.160 Manifest Version: 8.0.40/8.0.100 Manifest Path: C:\Program Files\dotnet\sdk-manifests\8.0.100\microsoft.net.sdk.maui\8.0.40\WorkloadManifest.json Install Type: Msi [aspire] Installation Source: VS 17.10.35013.160 Manifest Version: 8.0.0/8.0.100 Manifest Path: C:\Program Files\dotnet\sdk-manifests\8.0.100\microsoft.net.sdk.aspire\8.0.0\WorkloadManifest.json Install Type: Msi Host: Version: 8.0.6 Architecture: x64 Commit: 3b8b000a0e .NET SDKs installed: 8.0.106 [C:\Program Files\dotnet\sdk] 8.0.302 [C:\Program Files\dotnet\sdk] .NET runtimes installed: Microsoft.AspNetCore.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 6.0.31 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 7.0.20 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 8.0.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.NETCore.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 6.0.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 6.0.15 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 6.0.31 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 7.0.20 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 8.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.WindowsDesktop.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 6.0.15 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 6.0.31 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 7.0.20 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 8.0.6 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Other architectures found: x86 [C:\Program Files (x86)\dotnet] registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation] Environment variables: Not set global.json file: Not found Learn more: https://aka.ms/dotnet/info Download .NET: https://aka.ms/dotnet/downloadVisual Studio 2022 Info
Upon further request additional information may be made available based on relevancy.