Version Packages

[github-actions]

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@0.6.0

Minor Changes

• #371 5a287b2 Thanks @mikebarkmin! - # Introducing Hyperlibrary

  A Hyperlibrary is a way to connect multiple Hyperbooks and Hyperlibraries with
  each other. Hyperlibraries are a super flexible way to develop connected
  Hyperbooks.

  A Hyperlibrary is nothing more than a hyperlibrary.json files.
  Here is an example for connecting different versions.

  {
    "name": "Versions",
    "library": [
      { "src": "v1", "name": "1.0.0", "basePath": "v1" },
      { "src": "v2", "name": "2.0.0", "basePath": "/" }
    ]
  }

  The folder structure in this case would look like this:

  documention
  | v1
  | | ...
  | | hyperbook.json
  | v2
  | | ...
  | | hyperbook.json
  | hyperlibrary.json

  As for a Hyperbook, you also have to run the hyperbook setup first.
  Afterwards you can use the hyperbook build command for building your
  Hyperlibrary.

  The hyperbook dev command is not supported with this release. As a workaround you have to start the Hyperbooks as standalones. For example

  user ~/documention $ cd v1
  user ~/v1 $ npx hyperbook dev

  CLI Changes

  • hyperbook setup does not download the template any more from the GitHub repo, but bundles it. This should decrease bandwidth and improve setup speed.
  • hyperbook build and hyperbook setup received new command line outputs. This was necessary for not getting lost when using the CLI with a Hyperlibrary.

Patch Changes

• Updated dependencies [5a287b2]:
  • @hyperbook/types@0.3.0

@hyperbook/next-watch@0.1.0

Minor Changes

• #371 5a287b2 Thanks @mikebarkmin! - # Introducing Hyperlibrary

  A Hyperlibrary is a way to connect multiple Hyperbooks and Hyperlibraries with
  each other. Hyperlibraries are a super flexible way to develop connected
  Hyperbooks.

  A Hyperlibrary is nothing more than a hyperlibrary.json files.
  Here is an example for connecting different versions.

  {
    "name": "Versions",
    "library": [
      { "src": "v1", "name": "1.0.0", "basePath": "v1" },
      { "src": "v2", "name": "2.0.0", "basePath": "/" }
    ]
  }

  The folder structure in this case would look like this:

  documention
  | v1
  | | ...
  | | hyperbook.json
  | v2
  | | ...
  | | hyperbook.json
  | hyperlibrary.json

  As for a Hyperbook, you also have to run the hyperbook setup first.
  Afterwards you can use the hyperbook build command for building your
  Hyperlibrary.

  The hyperbook dev command is not supported with this release. As a workaround you have to start the Hyperbooks as standalones. For example

  user ~/documention $ cd v1
  user ~/v1 $ npx hyperbook dev

  CLI Changes

  • hyperbook setup does not download the template any more from the GitHub repo, but bundles it. This should decrease bandwidth and improve setup speed.
  • hyperbook build and hyperbook setup received new command line outputs. This was necessary for not getting lost when using the CLI with a Hyperlibrary.

Patch Changes

• Updated dependencies [5a287b2]:
  • @hyperbook/types@0.3.0

@hyperbook/types@0.3.0

Minor Changes

• #371 5a287b2 Thanks @mikebarkmin! - # Introducing Hyperlibrary

  A Hyperlibrary is a way to connect multiple Hyperbooks and Hyperlibraries with
  each other. Hyperlibraries are a super flexible way to develop connected
  Hyperbooks.

  A Hyperlibrary is nothing more than a hyperlibrary.json files.
  Here is an example for connecting different versions.

  {
    "name": "Versions",
    "library": [
      { "src": "v1", "name": "1.0.0", "basePath": "v1" },
      { "src": "v2", "name": "2.0.0", "basePath": "/" }
    ]
  }

  The folder structure in this case would look like this:

  documention
  | v1
  | | ...
  | | hyperbook.json
  | v2
  | | ...
  | | hyperbook.json
  | hyperlibrary.json

  As for a Hyperbook, you also have to run the hyperbook setup first.
  Afterwards you can use the hyperbook build command for building your
  Hyperlibrary.

  The hyperbook dev command is not supported with this release. As a workaround you have to start the Hyperbooks as standalones. For example

  user ~/documention $ cd v1
  user ~/v1 $ npx hyperbook dev

  CLI Changes

  • hyperbook setup does not download the template any more from the GitHub repo, but bundles it. This should decrease bandwidth and improve setup speed.
  • hyperbook build and hyperbook setup received new command line outputs. This was necessary for not getting lost when using the CLI with a Hyperlibrary.

@hyperbook/element-alert@0.1.7

Patch Changes

• Updated dependencies []:
  • @hyperbook/provider@0.1.7

@hyperbook/element-bitflow@0.1.8

Patch Changes

• Updated dependencies []:
  • @hyperbook/provider@0.1.7

@hyperbook/element-bookmarks@0.2.2

Patch Changes

• Updated dependencies []:
  • @hyperbook/provider@0.1.7

@hyperbook/element-collapsible@0.2.3

Patch Changes

• Updated dependencies []:
  • @hyperbook/provider@0.1.7

@hyperbook/element-dl@0.1.7

Patch Changes

• Updated dependencies []:
  • @hyperbook/provider@0.1.7

@hyperbook/element-excalidraw@0.2.2

Patch Changes

• Updated dependencies []:
  • @hyperbook/provider@0.1.7

@hyperbook/element-mermaid@0.1.7

Patch Changes

• Updated dependencies []:
  • @hyperbook/provider@0.1.7

@hyperbook/element-protect@0.2.2

Patch Changes

• Updated dependencies []:
  • @hyperbook/provider@0.1.7

@hyperbook/element-qr@0.1.8

Patch Changes

• Updated dependencies []:
  • @hyperbook/provider@0.1.7

@hyperbook/element-struktog@0.1.7

Patch Changes

• Updated dependencies []:
  • @hyperbook/provider@0.1.7

@hyperbook/element-tabs@0.1.8

Patch Changes

• Updated dependencies []:
  • @hyperbook/provider@0.1.7

@hyperbook/element-term@0.1.7

Patch Changes

• Updated dependencies []:
  • @hyperbook/provider@0.1.7

@hyperbook/element-youtube@0.1.7

Patch Changes

• Updated dependencies []:
  • @hyperbook/provider@0.1.7

@hyperbook/markdown@0.3.2

Patch Changes

• Updated dependencies []:
  • @hyperbook/provider@0.1.7

@hyperbook/provider@0.1.7

Patch Changes

• Updated dependencies [5a287b2]:
  • @hyperbook/types@0.3.0

@hyperbook/styles@0.1.7

Patch Changes

• Updated dependencies []:
  • @hyperbook/provider@0.1.7

hyperbook-simple-template@0.7.0

Minor Changes

• #371 5a287b2 Thanks @mikebarkmin! - # Introducing Hyperlibrary

  A Hyperlibrary is a way to connect multiple Hyperbooks and Hyperlibraries with
  each other. Hyperlibraries are a super flexible way to develop connected
  Hyperbooks.

  A Hyperlibrary is nothing more than a hyperlibrary.json files.
  Here is an example for connecting different versions.

  {
    "name": "Versions",
    "library": [
      { "src": "v1", "name": "1.0.0", "basePath": "v1" },
      { "src": "v2", "name": "2.0.0", "basePath": "/" }
    ]
  }

  The folder structure in this case would look like this:

  documention
  | v1
  | | ...
  | | hyperbook.json
  | v2
  | | ...
  | | hyperbook.json
  | hyperlibrary.json

  As for a Hyperbook, you also have to run the hyperbook setup first.
  Afterwards you can use the hyperbook build command for building your
  Hyperlibrary.

  The hyperbook dev command is not supported with this release. As a workaround you have to start the Hyperbooks as standalones. For example

  user ~/documention $ cd v1
  user ~/v1 $ npx hyperbook dev

  CLI Changes

  • hyperbook setup does not download the template any more from the GitHub repo, but bundles it. This should decrease bandwidth and improve setup speed.
  • hyperbook build and hyperbook setup received new command line outputs. This was necessary for not getting lost when using the CLI with a Hyperlibrary.

Patch Changes

• Updated dependencies []:
  • @hyperbook/provider@0.1.7
  • @hyperbook/element-alert@0.1.7
  • @hyperbook/element-bitflow@0.1.8
  • @hyperbook/element-bookmarks@0.2.2
  • @hyperbook/element-collapsible@0.2.3
  • @hyperbook/element-dl@0.1.7
  • @hyperbook/element-excalidraw@0.2.2
  • @hyperbook/element-mermaid@0.1.7
  • @hyperbook/element-protect@0.2.2
  • @hyperbook/element-qr@0.1.8
  • @hyperbook/element-struktog@0.1.7
  • @hyperbook/element-tabs@0.1.8
  • @hyperbook/element-term@0.1.7
  • @hyperbook/element-youtube@0.1.7
  • @hyperbook/markdown@0.3.2
  • @hyperbook/styles@0.1.7

hyperbook-studio@0.4.3

Patch Changes

• Updated dependencies []:
  • @hyperbook/provider@0.1.7
  • @hyperbook/element-alert@0.1.7
  • @hyperbook/element-bitflow@0.1.8
  • @hyperbook/element-bookmarks@0.2.2
  • @hyperbook/element-collapsible@0.2.3
  • @hyperbook/element-dl@0.1.7
  • @hyperbook/element-excalidraw@0.2.2
  • @hyperbook/element-mermaid@0.1.7
  • @hyperbook/element-protect@0.2.2
  • @hyperbook/element-qr@0.1.8
  • @hyperbook/element-struktog@0.1.7
  • @hyperbook/element-tabs@0.1.8
  • @hyperbook/element-term@0.1.7
  • @hyperbook/element-youtube@0.1.7
  • @hyperbook/markdown@0.3.2
  • @hyperbook/styles@0.1.7

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
hyperbook	✅ Ready (Inspect)	Visit Preview	Oct 21, 2022 at 11:46AM (UTC)