2017-10-16 17:15:08 -07:00
|
|
|
{
|
|
|
|
|
"name": "hexo-site",
|
|
|
|
|
"version": "0.0.0",
|
|
|
|
|
"private": true,
|
|
|
|
|
"hexo": {
|
2018-05-03 07:29:18 -07:00
|
|
|
"version": "3.7.1"
|
2017-10-16 17:15:08 -07:00
|
|
|
},
|
[docs] Use package-based Hexo theme, rather than a Git submodule. (#869)
* docs: Use `devDependencies` instead of `dependencies`.
It's safe to mark all dependencies of this theme as 'dev' dependencies, as
none of them are needed to be installed in a production setting.
This was done automatically, so in some cases, this merges existing
`devDependencies`, and may also have added a missing `nodemon` `devDependency`
in cases where it was missing. In other cases, this commit may not have
made such a change.
* docs: Remove _config.yml options now covered by global theme config.
* docs: Add `_multiconfig.yml`, a build artifact, to docs `.gitignore`.
* docs: Use theme from npm, rather than submodule, using `chexo`.
The theme which the docs in this repository are based on
([`hexo-theme-meteor`](https://github.com/meteor/hexo-theme-meteor)) has been
published to npm.
Additionally, most of the configuration which was once present in this
repository's `_config.yml` file, has been moved into an Apollo-centric theme
configuration npm,
[`apollo-hexo-config`](https://www.npmjs.com/package/apollo-hexo-config) (and
similarly, [GitHub](https://github.com/apollographql/apollo-hexo-config)).
The theme bundled in this npm is a converged version of the two `apollo`
and `master` branches on the `hexo-theme-meteor` repository, which is a result
of the work undertaken in https://github.com/meteor/hexo-theme-meteor/pull/51.
Lastly, this makes use of a new `chexo` npm which acts as a wrapper for `hexo`
but permits the use of an inherited configuration from npm, rather than a
statically defined CLI file parameter (previously with `--config a,b`).
* docs: Upgrade Hexo generator/tag/server dependencies.
* docs: Add missing `meteor-theme-hexo` package.
This was apparently missed, only on this repository (???) in my automated
commits, probably due to my own error.
2018-03-12 21:13:22 +02:00
|
|
|
"devDependencies": {
|
2018-07-10 16:18:55 -07:00
|
|
|
"apollo-hexo-config": "1.0.8",
|
2018-04-13 11:36:15 +00:00
|
|
|
"chexo": "1.0.5",
|
2018-10-19 07:33:39 +00:00
|
|
|
"hexo": "3.8.0",
|
2018-07-11 16:36:47 -07:00
|
|
|
"hexo-browsersync": "0.3.0",
|
2018-11-14 16:52:05 +02:00
|
|
|
"hexo-prism-plus": "1.1.0",
|
2018-02-28 13:22:07 +02:00
|
|
|
"hexo-renderer-ejs": "0.3.1",
|
[docs] Use package-based Hexo theme, rather than a Git submodule. (#869)
* docs: Use `devDependencies` instead of `dependencies`.
It's safe to mark all dependencies of this theme as 'dev' dependencies, as
none of them are needed to be installed in a production setting.
This was done automatically, so in some cases, this merges existing
`devDependencies`, and may also have added a missing `nodemon` `devDependency`
in cases where it was missing. In other cases, this commit may not have
made such a change.
* docs: Remove _config.yml options now covered by global theme config.
* docs: Add `_multiconfig.yml`, a build artifact, to docs `.gitignore`.
* docs: Use theme from npm, rather than submodule, using `chexo`.
The theme which the docs in this repository are based on
([`hexo-theme-meteor`](https://github.com/meteor/hexo-theme-meteor)) has been
published to npm.
Additionally, most of the configuration which was once present in this
repository's `_config.yml` file, has been moved into an Apollo-centric theme
configuration npm,
[`apollo-hexo-config`](https://www.npmjs.com/package/apollo-hexo-config) (and
similarly, [GitHub](https://github.com/apollographql/apollo-hexo-config)).
The theme bundled in this npm is a converged version of the two `apollo`
and `master` branches on the `hexo-theme-meteor` repository, which is a result
of the work undertaken in https://github.com/meteor/hexo-theme-meteor/pull/51.
Lastly, this makes use of a new `chexo` npm which acts as a wrapper for `hexo`
but permits the use of an inherited configuration from npm, rather than a
statically defined CLI file parameter (previously with `--config a,b`).
* docs: Upgrade Hexo generator/tag/server dependencies.
* docs: Add missing `meteor-theme-hexo` package.
This was apparently missed, only on this repository (???) in my automated
commits, probably due to my own error.
2018-03-12 21:13:22 +02:00
|
|
|
"hexo-renderer-less": "0.2.0",
|
2018-02-28 13:22:07 +02:00
|
|
|
"hexo-renderer-marked": "0.3.2",
|
2018-08-28 09:25:12 +00:00
|
|
|
"hexo-server": "0.3.3",
|
2018-11-12 20:26:16 +02:00
|
|
|
"meteor-theme-hexo": "2.0.1"
|
2017-10-16 17:15:08 -07:00
|
|
|
},
|
|
|
|
|
"scripts": {
|
[docs] Use package-based Hexo theme, rather than a Git submodule. (#869)
* docs: Use `devDependencies` instead of `dependencies`.
It's safe to mark all dependencies of this theme as 'dev' dependencies, as
none of them are needed to be installed in a production setting.
This was done automatically, so in some cases, this merges existing
`devDependencies`, and may also have added a missing `nodemon` `devDependency`
in cases where it was missing. In other cases, this commit may not have
made such a change.
* docs: Remove _config.yml options now covered by global theme config.
* docs: Add `_multiconfig.yml`, a build artifact, to docs `.gitignore`.
* docs: Use theme from npm, rather than submodule, using `chexo`.
The theme which the docs in this repository are based on
([`hexo-theme-meteor`](https://github.com/meteor/hexo-theme-meteor)) has been
published to npm.
Additionally, most of the configuration which was once present in this
repository's `_config.yml` file, has been moved into an Apollo-centric theme
configuration npm,
[`apollo-hexo-config`](https://www.npmjs.com/package/apollo-hexo-config) (and
similarly, [GitHub](https://github.com/apollographql/apollo-hexo-config)).
The theme bundled in this npm is a converged version of the two `apollo`
and `master` branches on the `hexo-theme-meteor` repository, which is a result
of the work undertaken in https://github.com/meteor/hexo-theme-meteor/pull/51.
Lastly, this makes use of a new `chexo` npm which acts as a wrapper for `hexo`
but permits the use of an inherited configuration from npm, rather than a
statically defined CLI file parameter (previously with `--config a,b`).
* docs: Upgrade Hexo generator/tag/server dependencies.
* docs: Add missing `meteor-theme-hexo` package.
This was apparently missed, only on this repository (???) in my automated
commits, probably due to my own error.
2018-03-12 21:13:22 +02:00
|
|
|
"start": "npm run build && chexo apollo-hexo-config -- server",
|
|
|
|
|
"build": "chexo apollo-hexo-config -- generate",
|
2018-02-28 13:22:07 +02:00
|
|
|
"clean": "hexo clean",
|
|
|
|
|
"test": "npm run clean; npm run build"
|
2018-04-26 23:01:34 +03:00
|
|
|
},
|
|
|
|
|
"dependencies": {
|
2018-11-15 13:11:30 +02:00
|
|
|
"hexo-versioned-netlify-redirects": "1.1.0"
|
2017-10-16 17:15:08 -07:00
|
|
|
}
|
|
|
|
|
}
|