[joantune]

Perhaps just give descriptive names and then change it when the scope changes??

"Problem" solved!

Afraid of losing stars/dlds on the repo/etc? Make it clear in the Readme where the new project is. Have warnings et al for NPM projects.

Ask npm/GitHub to allow name changes with redirects.

This proposed "solution" is just bad for many reasons:

You need to delve into the Readme to find out what it does. Imagine you're seeing a package.json and for each line you have to Google what's the project about

SEO is best if name matches.

These are enough *good* reasons why this advice is a bad idea

[lupire]

Renaming is work that doesn't improve the functionality.

[smsm42]

Only is you see "functionality" as "code being run in production". A lot of things then don't improve "functionality" - design documents, comments, use cases, tests, documentation, tutorials, etc. Proper software project still does all of it.

[xpe]

Functionality isn't all that matters. Software has many other aspects.