Prefixed "name" property in package.json is not supported?

[stcherenkov]

Hello!

When I name my theme @org/foo in package.json and check it with GScan, I get:

• Error: package.json property "name" must be hyphenated

Ghost really does not support package name with organization prefix for themes? Or is it GScan-only issue?

[naz]

Hi @stcherenkov! This is a gscan issue and after trying to activate some themes locally haven't found any issues with such naming. It's probably up for discussion if we should allow namespacing in theme naming as the current one has been established years ago ⏳

[stcherenkov]

Well, it looks like namespaces are a solid part of npm ecosystem now. This npm feature is also getting wide adoption by companies for private packages or publicly sourced packages with primary use inside company.

There is also a nice feature for Ghost theme developers – to be identified as an author of multiple themes by owning a named scope.

[mindsers]

Facing the same issue. Glad to see that it's only a GScan "issue".

[ErisDS]

We should fix this, but it needs a bit of a check to make sure that fixing it doesn't result in any breakages in e.g. Ghost Admin UI or theme handling code.