Moving packages into nuxt namespace/org

[manniL]

A dedicated request/suggestion issue for moving packages into the official namespace, monorepo and/or GitHub organization

[manniL]

opencollective

• Link: https://github.com/nuxt-community/opencollective
• Reason: Part of every Nuxt installation
• Move to @nuxt NPM scope: yes
• Move to monorepo: no
• Move to nuxt GH organization: yes

[manniL]

eslint-config

• Link: https://github.com/nuxt/eslint-config
• Reason: Tightly coupled to nuxt
• Move to @nuxt NPM scope: yes
• Move to monorepo: no
• Move to nuxt GH organization: already done

[manniL]

renovate-config-nuxt

• Link: https://github.com/nuxt/renovate-config-nuxt
• Reason: Tightly coupled to nuxt
• Move to @nuxt NPM scope: yes
• Move to monorepo: no
• Move to nuxt GH organization: already done

[pi0]

@manniL I suggest only have nuxt distribution related packages into monorepo. As because of "dependent" version they will have extra publishes.

[manniL]

@pi0 So keep the configs out of it?

[pi0]

@manniL Yes, that's my suggestion. I would call them something more than configs, "ecosystem utilities" :D

[manniL]

@pi0 fair enough! :+1:

[pi0]

opencollective moved to nuxt GH

[manniL]

@pi0 and published under both NPM scopes :relaxed:

[pi0]

@manniL Can we close this one?

[manniL]

@pi0 Well, eslint-config and renovate-config aren't released under the @nuxt scope. Do we want to keep them in @nuxtjs?

[pi0]

@manniL As they are commonly used for internal usage and community projects, I suggest keeping in @nuxtjs namespace.

[manniL]

Good, we can close it then ☺️