-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
293d86f
chore: migrate from lerna bootstrap to npm workspaces
JamesHenry 77a2186
chore: add missing npm install to readme
JamesHenry ebc36ab
Merge branch 'develop' into develop
sy-records a285bfd
chore: update readme
JamesHenry 71ece72
Merge branch 'develop' into develop
sy-records 1f95752
docs: change readme
sy-records 6f9aa1a
chore: ignore package-lock.json for docsify-server-renderer
sy-records 20896cf
Merge branch 'develop' into develop
trusktr File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
Show resolved
Hide resolved
|
||
"packages": [ | ||
trusktr marked this conversation as resolved.
Show resolved
Hide resolved
|
||
"packages/*" | ||
], | ||
"$schema": "node_modules/lerna/schemas/lerna-schema.json", | ||
trusktr marked this conversation as resolved.
Show resolved
Hide resolved
|
||
"version": "0.0.0" | ||
} |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 ci
natively 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
renderer
one 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:ssr
script 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
Docsify
component (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.