Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 5.8k
chore: migrate from lerna bootstrap to npm workspaces#2094
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
Changes from all commits
293d86f77a2186ebc36aba285bfd71ece721f957526f9aa1a20896cfFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -76,6 +76,10 @@ You can use Gitpod (a free online VS Code-like IDE) for contributing. With a sin | ||
| - install the dependencies. | ||
| - start `npm run dev`. | ||
| ```bash | ||
| npm install && npm run dev | ||
| ``` | ||
| So that you can start straight away. | ||
| [](https://gitpod.io/#https://github.com/docsifyjs/docsify) | ||
| @@ -86,12 +90,6 @@ So that you can start straight away. | ||
| - Push to the branch: `git push origin my-new-feature` | ||
| - Submit a pull request | ||
| ## Development | ||
| ```bash | ||
| npm run bootstrap && npm run dev | ||
sy-records marked this conversation as resolved.
Uh oh!There was an error while loading. Please reload this page. | ||
| ``` | ||
| ## Backers | ||
| Thank you to all our backers! 🙏 [[Become a backer](https://opencollective.com/docsify#backers)] | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,7 +1,4 @@ | ||
| { | ||
| "lerna": "2.0.0-rc.5", | ||
trusktr marked this conversation as resolved.
Uh oh!There was an error while loading. Please reload this page. | ||
| "packages": [ | ||
trusktr marked this conversation as resolved.
Uh oh!There was an error while loading. Please reload this page. | ||
| "packages/*" | ||
| ], | ||
| "$schema": "node_modules/lerna/schemas/lerna-schema.json", | ||
trusktr marked this conversation as resolved.
Uh oh!There was an error while loading. Please reload this page. | ||
| "version": "0.0.0" | ||
| } | ||
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is no longer needed,
npm cinatively understands workspaces and will install everything from the rootThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi James, we actually have 2 repos and the
rendererone is the subfolder of root but not a module. So we need run ci seperated for them.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @Koooooo-7, can you describe the issue here more?
What James is mentioning is that the above step,
also installs dependencies for server-renderer.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we're fine: I don't think many people (if any?) are using SSR, and our current
dev:ssrscript is even broken like so:I a new issue which should address this: #2102
I think it would be ok to merge this then fix any issues we may find, if we even care about them.
Even better: I recommend we just delete the SSR stuff because it is a pain to maintain that none of us have time for. In fact, install Docsify plugins and SSR breaks very easily. It is in a very alpha quality that we aren't using ourselves and honestly haven't cared for, so I think deleting SSR, and improving our code base (move to ESM, clean up some logic), would help us better prepare for thinking about the proper way to implement SSR.
If we decide to then restore SSR, I think we should convert to a
Docsifycomponent (f.e. using Solid.js, React, Vue, Svelte, or etc) and let a tool like Astro (maintained by a team of people who think about SSR and SSG all day every day, and are making the latest advancements in the area) give us the best SSR and SSG setup that we can simply ride upon. This will be very powerful, and without us having our own SSR implementation that doesn't work well and is far from complete.With this in mind, I would be ok to roll with this, as I tested non-SSR Docsify and the dev experience is working great.