Accept transfer of 'eleventy' npm namespace

[jokroese]

Is your feature request related to a problem? Please describe. I am new to the Eleventy project and I feel that the need to use @11ty/eleventy instead of eleventy in commands has a negative impact on onboarding beginners. (I would guess that it is also the tiniest bit annoying for novice users too.)

Given that the repository is 1) self-described as 'useless' and 2) has ~400 weekly downloads (20,000 a year!), I suspect many beginners have issues with installing the wrong software.

Describe the solution you'd like The owner of the repository has signalled an openness to transfer the eleventy npm namespace to this project (source: https://github.com/102/eleventy/issues/170). I think we should engage with the offer, attain the namespace and change all the documentation from @11ty/eleventy to eleventy.

Additional context I am not familiar with how this would work at an npm level. However, for backwards compatibility, we should ensure that either 1) npm sets up a redirect or 2) we maintain a mirror of eleventy at @11ty/eleventy.

[zachleat]

No harm to cc @102 here I guess!

[jokroese]

Paraphrasing @102, my understanding is that the next steps are for the @11ty community to answer two questions:

1. Is it useful for @11ty to have the eleventy npm namespace?
2. If so, how would a transfer work in practice?

[jokroese]

Focusing first on question 1, my intuition is that supporting the eleventy npm namespace would be useful (for onboarding, documentation, reduced cognitive load, branding etc.). However, I am new to the project and unfamiliar with any relevant history and concerns.

Do any of the longer-term contributors to the @11ty project have thoughts on this first question?

[zachleat]

Yeah, I absolutely think it’d be useful to have control of this—at the very least for security reasons with accidental installs