mentos1386/mnts.dev
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
mnts.dev/package.json

87 lines
2.2 KiB
JSON
Raw Normal View History

Added "package.json" file Includes "name" and "version" setting
2014-03-03 09:58:59 +00:00
{
📚 Expand package.json ready for gpm no issue - Our new marketplace (gpm) will make heavy use of package.json files - Full details, spec, and validator are coming soon. In the meantime here's the basics: - `name` must be lowercase and hypenated - `version` must be semver compliant - `homepage` should be a valid URL (GitHub URL is ok) - `demo` should be a working Ghost install that uses your theme - `engines` should contain a Ghost key indicating which version of Ghost the theme is compatible with - `license` is required, we recommend `MIT` - `screenshots` should provide a relative path or absolute URL to both `desktop` & `mobile` screenshots - `author` should be an object. It must contain an email, and can also include a name and url. - the `gpm` object should: - indicate the package type (`theme` for now, later `app` or `adapter` etc) - list out at most 2 marketplace categories for inclusion. Categories can be found in https://gist.github.com/ErisDS/d0674f57eaa087c9f92cbfc8e984d2d6 but are subject to change. - other fields can be included as per a normal npm package, we recommend including the repostory & keywords with `ghost` & `theme` listed.
2016-09-27 15:17:29 +00:00
"name": "casper",
"description": "The default personal blogging theme for Ghost. Beautiful, minimal and responsive.",
"demo": "https://demo.ghost.io",
Upgrading Casper to 2.9.2
2019-02-12 10:47:57 +00:00
"version": "2.9.2",
📚 Expand package.json ready for gpm no issue - Our new marketplace (gpm) will make heavy use of package.json files - Full details, spec, and validator are coming soon. In the meantime here's the basics: - `name` must be lowercase and hypenated - `version` must be semver compliant - `homepage` should be a valid URL (GitHub URL is ok) - `demo` should be a working Ghost install that uses your theme - `engines` should contain a Ghost key indicating which version of Ghost the theme is compatible with - `license` is required, we recommend `MIT` - `screenshots` should provide a relative path or absolute URL to both `desktop` & `mobile` screenshots - `author` should be an object. It must contain an email, and can also include a name and url. - the `gpm` object should: - indicate the package type (`theme` for now, later `app` or `adapter` etc) - list out at most 2 marketplace categories for inclusion. Categories can be found in https://gist.github.com/ErisDS/d0674f57eaa087c9f92cbfc8e984d2d6 but are subject to change. - other fields can be included as per a normal npm package, we recommend including the repostory & keywords with `ghost` & `theme` listed.
2016-09-27 15:17:29 +00:00
"engines": {
Bumped default Ghost API version to v2 no issue - This change is due to Content API becoming stable https://github.com/TryGhost/Ghost/releases/tag/2.10.0
2019-01-08 14:30:22 +00:00
"ghost": ">=2.0.0",
"ghost-api": "v2"
📚 Expand package.json ready for gpm no issue - Our new marketplace (gpm) will make heavy use of package.json files - Full details, spec, and validator are coming soon. In the meantime here's the basics: - `name` must be lowercase and hypenated - `version` must be semver compliant - `homepage` should be a valid URL (GitHub URL is ok) - `demo` should be a working Ghost install that uses your theme - `engines` should contain a Ghost key indicating which version of Ghost the theme is compatible with - `license` is required, we recommend `MIT` - `screenshots` should provide a relative path or absolute URL to both `desktop` & `mobile` screenshots - `author` should be an object. It must contain an email, and can also include a name and url. - the `gpm` object should: - indicate the package type (`theme` for now, later `app` or `adapter` etc) - list out at most 2 marketplace categories for inclusion. Categories can be found in https://gist.github.com/ErisDS/d0674f57eaa087c9f92cbfc8e984d2d6 but are subject to change. - other fields can be included as per a normal npm package, we recommend including the repostory & keywords with `ghost` & `theme` listed.
2016-09-27 15:17:29 +00:00
},
"license": "MIT",
"screenshots": {
"desktop": "assets/screenshot-desktop.jpg",
"mobile": "assets/screenshot-mobile.jpg"
},
Added yarn.lock and updated README for new yarn scripts no issue
2018-04-09 08:19:05 +00:00
"scripts": {
🛠 Added .travis.yml and gscan tests (#470) - Add gscan dependency & travis.yml file, so that we can run gscan as a test for this repo - This check tells us whether or not the theme is valid & compatible with Ghost according to gscan - We recommend that all themes do this!
2018-08-14 21:10:01 +00:00
"dev": "gulp",
"zip": "gulp zip",
Added "yarn ship" command no issue - @TODO: add the ability to draft a release when running `yarn ship`
2019-02-11 18:30:21 +00:00
"test": "gscan .",
"preship": "yarn test",
"ship": "STATUS=$(git status --porcelain); echo $STATUS; if [ -z \"$STATUS\" ]; then yarn version && git push --follow-tags; fi"
Added yarn.lock and updated README for new yarn scripts no issue
2018-04-09 08:19:05 +00:00
},
📚 Expand package.json ready for gpm no issue - Our new marketplace (gpm) will make heavy use of package.json files - Full details, spec, and validator are coming soon. In the meantime here's the basics: - `name` must be lowercase and hypenated - `version` must be semver compliant - `homepage` should be a valid URL (GitHub URL is ok) - `demo` should be a working Ghost install that uses your theme - `engines` should contain a Ghost key indicating which version of Ghost the theme is compatible with - `license` is required, we recommend `MIT` - `screenshots` should provide a relative path or absolute URL to both `desktop` & `mobile` screenshots - `author` should be an object. It must contain an email, and can also include a name and url. - the `gpm` object should: - indicate the package type (`theme` for now, later `app` or `adapter` etc) - list out at most 2 marketplace categories for inclusion. Categories can be found in https://gist.github.com/ErisDS/d0674f57eaa087c9f92cbfc8e984d2d6 but are subject to change. - other fields can be included as per a normal npm package, we recommend including the repostory & keywords with `ghost` & `theme` listed.
2016-09-27 15:17:29 +00:00
"author": {
"name": "Ghost Foundation",
"email": "hello@ghost.org",
"url": "https://ghost.org"
},
"gpm": {
"type": "theme",
"categories": [
"Minimal",
Clean up build tasks
2017-06-16 09:13:38 +00:00
"Magazine"
📚 Expand package.json ready for gpm no issue - Our new marketplace (gpm) will make heavy use of package.json files - Full details, spec, and validator are coming soon. In the meantime here's the basics: - `name` must be lowercase and hypenated - `version` must be semver compliant - `homepage` should be a valid URL (GitHub URL is ok) - `demo` should be a working Ghost install that uses your theme - `engines` should contain a Ghost key indicating which version of Ghost the theme is compatible with - `license` is required, we recommend `MIT` - `screenshots` should provide a relative path or absolute URL to both `desktop` & `mobile` screenshots - `author` should be an object. It must contain an email, and can also include a name and url. - the `gpm` object should: - indicate the package type (`theme` for now, later `app` or `adapter` etc) - list out at most 2 marketplace categories for inclusion. Categories can be found in https://gist.github.com/ErisDS/d0674f57eaa087c9f92cbfc8e984d2d6 but are subject to change. - other fields can be included as per a normal npm package, we recommend including the repostory & keywords with `ghost` & `theme` listed.
2016-09-27 15:17:29 +00:00
]
},
"keywords": [
"ghost",
✨Added required "ghost-theme" keyword - We're going to start showing this as a warning in gscan - The purpose is to give us a way to detect if a package is a valid Ghost theme
2018-08-13 13:29:56 +00:00
"theme",
"ghost-theme"
📚 Expand package.json ready for gpm no issue - Our new marketplace (gpm) will make heavy use of package.json files - Full details, spec, and validator are coming soon. In the meantime here's the basics: - `name` must be lowercase and hypenated - `version` must be semver compliant - `homepage` should be a valid URL (GitHub URL is ok) - `demo` should be a working Ghost install that uses your theme - `engines` should contain a Ghost key indicating which version of Ghost the theme is compatible with - `license` is required, we recommend `MIT` - `screenshots` should provide a relative path or absolute URL to both `desktop` & `mobile` screenshots - `author` should be an object. It must contain an email, and can also include a name and url. - the `gpm` object should: - indicate the package type (`theme` for now, later `app` or `adapter` etc) - list out at most 2 marketplace categories for inclusion. Categories can be found in https://gist.github.com/ErisDS/d0674f57eaa087c9f92cbfc8e984d2d6 but are subject to change. - other fields can be included as per a normal npm package, we recommend including the repostory & keywords with `ghost` & `theme` listed.
2016-09-27 15:17:29 +00:00
],
"repository": {
"type": "git",
🐛 Fixing package.json engines & repo URL no issue - semver caret ranges don't apply pre-1.0.0, therefore we need to use a more explicit range - repo URL should be a valid url
2016-10-07 15:05:10 +00:00
"url": "https://github.com/TryGhost/Casper.git"
📚 Expand package.json ready for gpm no issue - Our new marketplace (gpm) will make heavy use of package.json files - Full details, spec, and validator are coming soon. In the meantime here's the basics: - `name` must be lowercase and hypenated - `version` must be semver compliant - `homepage` should be a valid URL (GitHub URL is ok) - `demo` should be a working Ghost install that uses your theme - `engines` should contain a Ghost key indicating which version of Ghost the theme is compatible with - `license` is required, we recommend `MIT` - `screenshots` should provide a relative path or absolute URL to both `desktop` & `mobile` screenshots - `author` should be an object. It must contain an email, and can also include a name and url. - the `gpm` object should: - indicate the package type (`theme` for now, later `app` or `adapter` etc) - list out at most 2 marketplace categories for inclusion. Categories can be found in https://gist.github.com/ErisDS/d0674f57eaa087c9f92cbfc8e984d2d6 but are subject to change. - other fields can be included as per a normal npm package, we recommend including the repostory & keywords with `ghost` & `theme` listed.
2016-09-27 15:17:29 +00:00
},
"bugs": "https://github.com/TryGhost/Casper/issues",
First pass 2.0 design
2017-05-15 20:03:47 +00:00
"contributors": "https://github.com/TryGhost/Casper/graphs/contributors",
"devDependencies": {
"autoprefixer": "6.3.6",
Updated gulp to handle errors for every stream (#500) no-issue Previously we only added an error handler to the first stream in each pipeline, this meant that if another stream errors you would get unhelpful error handlers.
2019-01-22 11:00:10 +00:00
"beeper": "^1.1.1",
First pass 2.0 design
2017-05-15 20:03:47 +00:00
"cssnano": "3.7.1",
🛠 Added .travis.yml and gscan tests (#470) - Add gscan dependency & travis.yml file, so that we can run gscan as a test for this repo - This check tells us whether or not the theme is valid & compatible with Ghost according to gscan - We recommend that all themes do this!
2018-08-14 21:10:01 +00:00
"gscan": "^2.0.0",
First pass 2.0 design
2017-05-15 20:03:47 +00:00
"gulp": "3.9.1",
Updated gulp to handle errors for every stream (#500) no-issue Previously we only added an error handler to the first stream in each pipeline, this meant that if another stream errors you would get unhelpful error handlers.
2019-01-22 11:00:10 +00:00
"gulp-filter": "5.1.0",
First pass 2.0 design
2017-05-15 20:03:47 +00:00
"gulp-livereload": "3.8.1",
"gulp-postcss": "6.1.1",
"gulp-sourcemaps": "1.6.0",
Updated gulp to handle errors for every stream (#500) no-issue Previously we only added an error handler to the first stream in each pipeline, this meant that if another stream errors you would get unhelpful error handlers.
2019-01-22 11:00:10 +00:00
"gulp-uglify": "3.0.1",
First pass 2.0 design
2017-05-15 20:03:47 +00:00
"gulp-watch": "4.3.8",
Add a Gulp task to create the zip (#374)
2017-09-18 16:37:00 +00:00
"gulp-zip": "4.0.0",
First pass 2.0 design
2017-05-15 20:03:47 +00:00
"postcss-color-function": "2.0.1",
"postcss-custom-properties": "5.0.1",
Minified javascript in zip(#476) no issue * Added js minification step to gulp zip script
2018-10-08 11:04:07 +00:00
"postcss-easy-import": "1.0.1",
Updated gulp to handle errors for every stream (#500) no-issue Previously we only added an error handler to the first stream in each pipeline, this meant that if another stream errors you would get unhelpful error handlers.
2019-01-22 11:00:10 +00:00
"pump": "3.0.0"
First pass 2.0 design
2017-05-15 20:03:47 +00:00
},
"config": {
Responsive images (#505)
2018-12-17 12:25:57 +00:00
"posts_per_page": 25,
"image_sizes": {
"xxs": {
"width": 30
},
"xs": {
"width": 100
},
"s": {
"width": 300
},
"m": {
"width": 600
},
"l": {
"width": 1000
},
"xl": {
"width": 2000
}
}
First pass 2.0 design
2017-05-15 20:03:47 +00:00
}
Version bump to 0.9.3
2014-03-20 19:17:26 +00:00
}
Reference in a new issue Copy permalink