feat: npm init docusaurus, yarn create docusaurus #5635
Conversation
|
✔️ [V2] 🔨 Explore the source changes: 1c68910 🔍 Inspect the deploy log: https://app.netlify.com/sites/docusaurus-2/deploys/615736ef5cf7750008d17785 😎 Browse the preview: https://deploy-preview-5635--docusaurus-2.netlify.app |
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-5635--docusaurus-2.netlify.app/ |
|
Size Change: +707 B (0%) Total Size: 834 kB
ℹ️ View Unchanged
|
|
✔️ [V2] 🔨 Explore the source changes: 8186a50 🔍 Inspect the deploy log: https://app.netlify.com/sites/docusaurus-2/deploys/615efd2c1bfe5200070b12a5 😎 Browse the preview: https://deploy-preview-5635--docusaurus-2.netlify.app |
| "name": "@docusaurus/init", | ||
| "version": "2.0.0-beta.6", | ||
| "name": "create-docusaurus", | ||
| "version": "0.0.6", |
There was a problem hiding this comment.
Thanks
Just because I did some test publish attempt to make sure it works and wanted to keep the ability to increment if needed
This will be fixed on next release by lerna so it doesn't matter
…d yarn result fails to execute
|
Reverting |
Motivation
Our init command is complex to type / remember:
Using the package name
create-docusaurusand{isDefault: true}allows to simplify it greatly:npx create-docusaurusalso worksAs this package is outside of
@docusaurusorg, I assigned proper roles on npm to the existing team.Unfortunately, we need to keep
@latestdue to npm: npm/cli#3821Have you read the Contributing Guidelines on pull requests?
yes
Test Plan
init tests + e2e CI tests