Version Packages - #1160
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@hyperbook/fs@0.26.0
Minor Changes
#1159
9bdb389Thanks @mikebarkmin! - Order pages and sections together byindex. Pages were always rendered beforethe sections of the same level, so a page could not sit after or between them.
The
indexof a page and theindexof a section are now one order, and asection that ends up between two pages is rendered between them.
The reading order follows the navigation, so the previous and next buttons, the
breadcrumb and
::pagelistagree with the sidebar.A page or a section without an
indexkeeps its old place: pages come beforesections, and a page wins a tie against a section. A book that gives its
sections an
indexbut leaves it off a page will see that page move behindthose sections. Give the page an
indexto place it.hyperbook@0.102.0
Minor Changes
#1159
9bdb389Thanks @mikebarkmin! - Order pages and sections together byindex. Pages were always rendered beforethe sections of the same level, so a page could not sit after or between them.
The
indexof a page and theindexof a section are now one order, and asection that ends up between two pages is rendered between them.
The reading order follows the navigation, so the previous and next buttons, the
breadcrumb and
::pagelistagree with the sidebar.A page or a section without an
indexkeeps its old place: pages come beforesections, and a page wins a tie against a section. A book that gives its
sections an
indexbut leaves it off a page will see that page move behindthose sections. Give the page an
indexto place it.Patch Changes
#1159
9bdb389Thanks @mikebarkmin! - Inline the script that loads the light and dark stylesheets. It was a file, andnothing can paint before the stylesheets it writes are there, so every first
paint waited for a round trip to fetch 1.5 kB and then another for the
stylesheets themselves. It is part of the page now, which measured about 140 ms
off the first contentful paint of the documentation on a throttled connection.
#1159
9bdb389Thanks @mikebarkmin! - Fix the drawers flashing over the page while it loads. A custom element rendersits children until it is upgraded, and a side drawer is only hidden by its
shadow root, so the search drawer and the table of contents drawer painted over
the header and the article until
side-drawer.jshad run.#1159
9bdb389Thanks @mikebarkmin! - Order the pages and the subsections of a section together too. Only the toplevel of the navigation shared one order, so inside a section a subsection was
still rendered after every page of that section, and the sidebar disagreed with
the previous and next buttons, which already followed the index.
#1159
9bdb389Thanks @mikebarkmin! - Indent the pages of a section in the navigation. They sat one pixel to theright of a page of the level above, so only a hairline told the two levels
apart. That was harmless while every page came before every section, but a page
can sit after a section now, and it has to be readable as a page of the level
above.
@hyperbook/markdown@0.73.0
Minor Changes
#1159
9bdb389Thanks @mikebarkmin! - Order pages and sections together byindex. Pages were always rendered beforethe sections of the same level, so a page could not sit after or between them.
The
indexof a page and theindexof a section are now one order, and asection that ends up between two pages is rendered between them.
The reading order follows the navigation, so the previous and next buttons, the
breadcrumb and
::pagelistagree with the sidebar.A page or a section without an
indexkeeps its old place: pages come beforesections, and a page wins a tie against a section. A book that gives its
sections an
indexbut leaves it off a page will see that page move behindthose sections. Give the page an
indexto place it.Patch Changes
#1159
9bdb389Thanks @mikebarkmin! - Inline the script that loads the light and dark stylesheets. It was a file, andnothing can paint before the stylesheets it writes are there, so every first
paint waited for a round trip to fetch 1.5 kB and then another for the
stylesheets themselves. It is part of the page now, which measured about 140 ms
off the first contentful paint of the documentation on a throttled connection.
#1159
9bdb389Thanks @mikebarkmin! - Fix the drawers flashing over the page while it loads. A custom element rendersits children until it is upgraded, and a side drawer is only hidden by its
shadow root, so the search drawer and the table of contents drawer painted over
the header and the article until
side-drawer.jshad run.#1159
9bdb389Thanks @mikebarkmin! - Order the pages and the subsections of a section together too. Only the toplevel of the navigation shared one order, so inside a section a subsection was
still rendered after every page of that section, and the sidebar disagreed with
the previous and next buttons, which already followed the index.
#1159
9bdb389Thanks @mikebarkmin! - Indent the pages of a section in the navigation. They sat one pixel to theright of a page of the level above, so only a hairline told the two levels
apart. That was harmless while every page came before every section, but a page
can sit after a section now, and it has to be readable as a page of the level
above.
@hyperbook/types@0.24.0
Minor Changes
#1159
9bdb389Thanks @mikebarkmin! - Order pages and sections together byindex. Pages were always rendered beforethe sections of the same level, so a page could not sit after or between them.
The
indexof a page and theindexof a section are now one order, and asection that ends up between two pages is rendered between them.
The reading order follows the navigation, so the previous and next buttons, the
breadcrumb and
::pagelistagree with the sidebar.A page or a section without an
indexkeeps its old place: pages come beforesections, and a page wins a tie against a section. A book that gives its
sections an
indexbut leaves it off a page will see that page move behindthose sections. Give the page an
indexto place it.create-hyperbook@0.3.10
Patch Changes
9bdb389]:hyperbook-studio@0.53.0
Minor Changes
#1159
9bdb389Thanks @mikebarkmin! - Order pages and sections together byindex. Pages were always rendered beforethe sections of the same level, so a page could not sit after or between them.
The
indexof a page and theindexof a section are now one order, and asection that ends up between two pages is rendered between them.
The reading order follows the navigation, so the previous and next buttons, the
breadcrumb and
::pagelistagree with the sidebar.A page or a section without an
indexkeeps its old place: pages come beforesections, and a page wins a tie against a section. A book that gives its
sections an
indexbut leaves it off a page will see that page move behindthose sections. Give the page an
indexto place it.Patch Changes
#1159
9bdb389Thanks @mikebarkmin! - Inline the script that loads the light and dark stylesheets. It was a file, andnothing can paint before the stylesheets it writes are there, so every first
paint waited for a round trip to fetch 1.5 kB and then another for the
stylesheets themselves. It is part of the page now, which measured about 140 ms
off the first contentful paint of the documentation on a throttled connection.
#1159
9bdb389Thanks @mikebarkmin! - Fix the drawers flashing over the page while it loads. A custom element rendersits children until it is upgraded, and a side drawer is only hidden by its
shadow root, so the search drawer and the table of contents drawer painted over
the header and the article until
side-drawer.jshad run.#1159
9bdb389Thanks @mikebarkmin! - Order the pages and the subsections of a section together too. Only the toplevel of the navigation shared one order, so inside a section a subsection was
still rendered after every page of that section, and the sidebar disagreed with
the previous and next buttons, which already followed the index.
#1159
9bdb389Thanks @mikebarkmin! - Indent the pages of a section in the navigation. They sat one pixel to theright of a page of the level above, so only a hairline told the two levels
apart. That was harmless while every page came before every section, but a page
can sit after a section now, and it has to be readable as a page of the level
above.
Updated dependencies [
9bdb389,9bdb389,9bdb389,9bdb389,9bdb389]: