[ ] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠️ Breaking change (fix or feature that would cause existing functionality to change)
📚 Description
There are many examples in our Nitro project inside examples folder. For example, in the api-routes folder, the name of the project is example-api-routes in the name field in package.json file. In the same way, in the auto-imports folder, the name in package.json is example-auto-imports. In the cached-handler folder, the name field in package.json is example-cached-handler. But in the websocket folder, the project name was given example-hello-world. I think it would be better to change it to example-websocket for maintaining the naming consistency like all other the projects in package.json.
🔗 Linked issue
❓ Type of change
📚 Description
There are many examples in our Nitro project inside
examplesfolder. For example, in theapi-routesfolder, the name of the project isexample-api-routesin thenamefield in package.json file. In the same way, in theauto-importsfolder, thenamein package.json isexample-auto-imports. In thecached-handlerfolder, thenamefield in package.json isexample-cached-handler. But in thewebsocketfolder, the project name was givenexample-hello-world. I think it would be better to change it toexample-websocketfor maintaining the naming consistency like all other the projects in package.json.📝 Checklist