[playground] Bug Fix: change default dev port to 3000

[etrepum]

Description

npm run dev (and associated npm run start) used to start on port 3000, which was the old vite default. The default changed to 5173, but no reason we can't keep the previous behavior #6018 (review)

Test plan

Before

npm run dev listens on port 5173 (after #6018 was merged)

After

• npm run dev listens on port 3000
• tests and other commands that also specify a port still get the desired choice

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
lexical	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 4, 2024 6:13pm
lexical-playground	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 4, 2024 6:13pm

[ivailop7]

Does it make sense to put the port in the vite config file, rather than extend the npm scripts. I think it's cleaner, no strong opinion on this. Approved.

[zurfyx]

Thank you for quick follow-up!

[etrepum]

@ivailop7 I also don't have a strong opinion about it either way. server: {port: 3000} in the vite.config.ts does that. If you specify multiple ports on the command line it takes the last one, so practically speaking other than where the setting is it's not a very observable difference. We manually specify the port elsewhere in the package.json files so I just did it in the same place.

[ivailop7]

@ivailop7 I also don't have a strong opinion about it either way. server: {port: 3000} in the vite.config.ts does that. If you specify multiple ports on the command line it takes the last one, so practically speaking other than where the setting is it's not a very observable difference. We manually specify the port elsewhere in the package.json files so I just did it in the same place.

Fair enough