2014-02-09 19:29:23 +04:00
|
|
|
{
|
2015-05-06 02:54:23 +03:00
|
|
|
"name": "ghost",
|
2016-11-17 23:15:19 +03:00
|
|
|
"version": "1.0.0-alpha.9",
|
2015-05-06 02:54:23 +03:00
|
|
|
"description": "Just a blogging platform.",
|
|
|
|
|
"author": "Ghost Foundation",
|
|
|
|
|
"homepage": "http://ghost.org",
|
|
|
|
|
"keywords": [
|
|
|
|
|
"ghost",
|
|
|
|
|
"blog",
|
|
|
|
|
"cms"
|
|
|
|
|
],
|
|
|
|
|
"repository": {
|
|
|
|
|
"type": "git",
|
|
|
|
|
"url": "git://github.com/TryGhost/Ghost.git"
|
|
|
|
|
},
|
|
|
|
|
"bugs": "https://github.com/TryGhost/Ghost/issues",
|
|
|
|
|
"contributors": "https://github.com/TryGhost/Ghost/graphs/contributors",
|
2015-05-26 07:00:32 +03:00
|
|
|
"license": "MIT",
|
2015-05-06 02:54:23 +03:00
|
|
|
"main": "./core/index",
|
|
|
|
|
"scripts": {
|
|
|
|
|
"start": "node index",
|
|
|
|
|
"test": "grunt validate --verbose"
|
|
|
|
|
},
|
|
|
|
|
"engines": {
|
2016-09-15 15:10:40 +03:00
|
|
|
"node": "~0.12.0 || ^4.2.0 || ^6.5.0"
|
2015-05-06 02:54:23 +03:00
|
|
|
},
|
|
|
|
|
"dependencies": {
|
2016-11-05 20:14:43 +03:00
|
|
|
"amperize": "1.0.0",
|
2017-01-04 15:54:41 +03:00
|
|
|
"archiver": "1.3.0",
|
2015-10-12 23:32:39 +03:00
|
|
|
"bcryptjs": "2.3.0",
|
2016-09-19 14:38:57 +03:00
|
|
|
"bluebird": "3.4.6",
|
2016-06-30 00:23:03 +03:00
|
|
|
"body-parser": "1.15.2",
|
2016-11-10 13:50:03 +03:00
|
|
|
"brute-knex": "https://github.com/cobbspur/brute-knex/tarball/0cb28fa8e3230dcbf6bca8b991dbb340b9fff6cc",
|
✨ replace auto increment id's by object id (#7495)
* 🛠 bookshelf tarball, bson-objectid
* 🎨 schema changes
- change increment type to string
- add a default fallback for string length 191 (to avoid adding this logic to every single column which uses an ID)
- remove uuid, because ID now represents a global resource identifier
- keep uuid for post, because we are using this as preview id
- keep uuid for clients for now - we are using this param for Ghost-Auth
* ✨ base model: generate ObjectId on creating event
- each new resource get's a auto generate ObjectId
- this logic won't work for attached models, this commit comes later
* 🎨 centralised attach method
When attaching models there are two things important two know
1. To be able to attach an ObjectId, we need to register the `onCreating` event the fetched model!This is caused by the Bookshelf design in general. On this target model we are attaching the new model.
2. We need to manually fetch the target model, because Bookshelf has a weird behaviour (which is known as a bug, see see https://github.com/tgriesser/bookshelf/issues/629). The most important property when attaching a model is `parentFk`, which is the foreign key. This can be null when fetching the model with the option `withRelated`. To ensure quality and consistency, the custom attach wrapper always fetches the target model manual. By fetching the target model (again) is a little performance decrease, but it also has advantages: we can register the event, and directly unregister the event again. So very clean code.
Important: please only use the custom attach wrapper in the future.
* 🎨 token model had overriden the onCreating function because of the created_at field
- we need to ensure that the base onCreating hook get's triggered for ALL models
- if not, they don't get an ObjectId assigned
- in this case: be smart and check if the target model has a created_at field
* 🎨 we don't have a uuid field anymore, remove the usages
- no default uuid creation in models
- i am pretty sure we have some more definitions in our tests (for example in the export json files), but that is too much work to delete them all
* 🎨 do not parse ID to Number
- we had various occurances of parsing all ID's to numbers
- we don't need this behaviour anymore
- ID is string
- i will adapt the ID validation in the next commit
* 🎨 change ID regex for validation
- we only allow: ID as ObjectId, ID as 1 and ID as me
- we need to keep ID 1, because our whole software relies on ID 1 (permissions etc)
* 🎨 owner fixture
- roles: [4] does not work anymore
- 4 means -> static id 4
- this worked in an auto increment system (not even in a system with distributed writes)
- with ObjectId we generate each ID automatically (for static and dynamic resources)
- it is possible to define all id's for static resources still, but that means we need to know which ID is already used and for consistency we have to define ObjectId's for these static resources
- so no static id's anymore, except of: id 1 for owner and id 0 for external usage (because this is required from our permission system)
- NOTE: please read through the comment in the user model
* 🎨 tests: DataGenerator and test utils
First of all: we need to ensure using ObjectId's in the tests. When don't, we can't ensure that ObjectId's work properly.
This commit brings lot's of dynamic into all the static defined id's.
In one of the next commits, i will adapt all the tests.
* 🚨 remove counter in Notification API
- no need to add a counter
- we simply generate ObjectId's (they are auto incremental as well)
- our id validator does only allow ObjectId as id,1 and me
* 🎨 extend contextUser in Base Model
- remove isNumber check, because id's are no longer numbers, except of id 0/1
- use existing isExternalUser
- support id 0/1 as string or number
* ✨ Ghost Owner has id 1
- ensure we define this id in the fixtures.json
- doesn't matter if number or string
* 🎨 functional tests adaptions
- use dynamic id's
* 🎨 fix unit tests
* 🎨 integration tests adaptions
* 🎨 change importer utils
- all our export examples (test/fixtures/exports) contain id's as numbers
- fact: but we ignore them anyway when inserting into the database, see https://github.com/TryGhost/Ghost/blob/master/core/server/data/import/utils.js#L249
- in https://github.com/TryGhost/Ghost/pull/7495/commits/0e6ed957cd54dc02a25cf6fb1ab7d7e723295e2c#diff-70f514a06347c048648be464819503c4L67 i removed parsing id's to integers
- i realised that this ^ check just existed, because the userIdToMap was an object key and object keys are always strings!
- i think this logic is a little bit complicated, but i don't want to refactor this now
- this commit ensures when trying to find the user, the id comparison works again
- i've added more documentation to understand this logic ;)
- plus i renamed an attribute to improve readability
* 🎨 Data-Generator: add more defaults to createUser
- if i use the function DataGenerator.forKnex.createUser i would like to get a full set of defaults
* 🎨 test utils: change/extend function set for functional tests
- functional tests work a bit different
- they boot Ghost and seed the database
- some functional tests have mis-used the test setup
- the test setup needs two sections: integration/unit and functional tests
- any functional test is allowed to either add more data or change data in the existing Ghost db
- but what it should not do is: add test fixtures like roles or users from our DataGenerator and cross fingers it will work
- this commit adds a clean method for functional tests to add extra users
* 🎨 functional tests adaptions
- use last commit to insert users for functional tests clean
- tidy up usage of testUtils.setup or testUtils.doAuth
* 🐛 test utils: reset database before init
- ensure we don't have any left data from other tests in the database when starting ghost
* 🐛 fix test (unrelated to this PR)
- fixes a random failure
- return statement was missing
* 🎨 make changes for invites
2016-11-17 12:09:11 +03:00
|
|
|
"bookshelf": "https://github.com/kirrg001/bookshelf/tarball/feature/creating-event-attached-models",
|
2016-10-04 18:33:43 +03:00
|
|
|
"bunyan": "1.8.1",
|
✨ replace auto increment id's by object id (#7495)
* 🛠 bookshelf tarball, bson-objectid
* 🎨 schema changes
- change increment type to string
- add a default fallback for string length 191 (to avoid adding this logic to every single column which uses an ID)
- remove uuid, because ID now represents a global resource identifier
- keep uuid for post, because we are using this as preview id
- keep uuid for clients for now - we are using this param for Ghost-Auth
* ✨ base model: generate ObjectId on creating event
- each new resource get's a auto generate ObjectId
- this logic won't work for attached models, this commit comes later
* 🎨 centralised attach method
When attaching models there are two things important two know
1. To be able to attach an ObjectId, we need to register the `onCreating` event the fetched model!This is caused by the Bookshelf design in general. On this target model we are attaching the new model.
2. We need to manually fetch the target model, because Bookshelf has a weird behaviour (which is known as a bug, see see https://github.com/tgriesser/bookshelf/issues/629). The most important property when attaching a model is `parentFk`, which is the foreign key. This can be null when fetching the model with the option `withRelated`. To ensure quality and consistency, the custom attach wrapper always fetches the target model manual. By fetching the target model (again) is a little performance decrease, but it also has advantages: we can register the event, and directly unregister the event again. So very clean code.
Important: please only use the custom attach wrapper in the future.
* 🎨 token model had overriden the onCreating function because of the created_at field
- we need to ensure that the base onCreating hook get's triggered for ALL models
- if not, they don't get an ObjectId assigned
- in this case: be smart and check if the target model has a created_at field
* 🎨 we don't have a uuid field anymore, remove the usages
- no default uuid creation in models
- i am pretty sure we have some more definitions in our tests (for example in the export json files), but that is too much work to delete them all
* 🎨 do not parse ID to Number
- we had various occurances of parsing all ID's to numbers
- we don't need this behaviour anymore
- ID is string
- i will adapt the ID validation in the next commit
* 🎨 change ID regex for validation
- we only allow: ID as ObjectId, ID as 1 and ID as me
- we need to keep ID 1, because our whole software relies on ID 1 (permissions etc)
* 🎨 owner fixture
- roles: [4] does not work anymore
- 4 means -> static id 4
- this worked in an auto increment system (not even in a system with distributed writes)
- with ObjectId we generate each ID automatically (for static and dynamic resources)
- it is possible to define all id's for static resources still, but that means we need to know which ID is already used and for consistency we have to define ObjectId's for these static resources
- so no static id's anymore, except of: id 1 for owner and id 0 for external usage (because this is required from our permission system)
- NOTE: please read through the comment in the user model
* 🎨 tests: DataGenerator and test utils
First of all: we need to ensure using ObjectId's in the tests. When don't, we can't ensure that ObjectId's work properly.
This commit brings lot's of dynamic into all the static defined id's.
In one of the next commits, i will adapt all the tests.
* 🚨 remove counter in Notification API
- no need to add a counter
- we simply generate ObjectId's (they are auto incremental as well)
- our id validator does only allow ObjectId as id,1 and me
* 🎨 extend contextUser in Base Model
- remove isNumber check, because id's are no longer numbers, except of id 0/1
- use existing isExternalUser
- support id 0/1 as string or number
* ✨ Ghost Owner has id 1
- ensure we define this id in the fixtures.json
- doesn't matter if number or string
* 🎨 functional tests adaptions
- use dynamic id's
* 🎨 fix unit tests
* 🎨 integration tests adaptions
* 🎨 change importer utils
- all our export examples (test/fixtures/exports) contain id's as numbers
- fact: but we ignore them anyway when inserting into the database, see https://github.com/TryGhost/Ghost/blob/master/core/server/data/import/utils.js#L249
- in https://github.com/TryGhost/Ghost/pull/7495/commits/0e6ed957cd54dc02a25cf6fb1ab7d7e723295e2c#diff-70f514a06347c048648be464819503c4L67 i removed parsing id's to integers
- i realised that this ^ check just existed, because the userIdToMap was an object key and object keys are always strings!
- i think this logic is a little bit complicated, but i don't want to refactor this now
- this commit ensures when trying to find the user, the id comparison works again
- i've added more documentation to understand this logic ;)
- plus i renamed an attribute to improve readability
* 🎨 Data-Generator: add more defaults to createUser
- if i use the function DataGenerator.forKnex.createUser i would like to get a full set of defaults
* 🎨 test utils: change/extend function set for functional tests
- functional tests work a bit different
- they boot Ghost and seed the database
- some functional tests have mis-used the test setup
- the test setup needs two sections: integration/unit and functional tests
- any functional test is allowed to either add more data or change data in the existing Ghost db
- but what it should not do is: add test fixtures like roles or users from our DataGenerator and cross fingers it will work
- this commit adds a clean method for functional tests to add extra users
* 🎨 functional tests adaptions
- use last commit to insert users for functional tests clean
- tidy up usage of testUtils.setup or testUtils.doAuth
* 🐛 test utils: reset database before init
- ensure we don't have any left data from other tests in the database when starting ghost
* 🐛 fix test (unrelated to this PR)
- fixes a random failure
- return statement was missing
* 🎨 make changes for invites
2016-11-17 12:09:11 +03:00
|
|
|
"bson-objectid": "1.1.4",
|
2016-04-21 12:19:55 +03:00
|
|
|
"chalk": "1.1.3",
|
2016-09-19 14:32:40 +03:00
|
|
|
"cheerio": "0.22.0",
|
2016-10-10 15:27:31 +03:00
|
|
|
"commander": "2.9.0",
|
2016-05-20 13:34:19 +03:00
|
|
|
"compression": "1.6.2",
|
2015-06-03 14:15:11 +03:00
|
|
|
"connect-slashes": "1.3.1",
|
2015-10-13 23:33:07 +03:00
|
|
|
"cookie-session": "1.2.0",
|
2016-09-14 15:16:18 +03:00
|
|
|
"cors": "2.8.1",
|
2016-09-19 13:25:37 +03:00
|
|
|
"csv-parser": "1.11.0",
|
2016-10-03 11:33:14 +03:00
|
|
|
"debug": "2.2.0",
|
2015-05-06 02:54:23 +03:00
|
|
|
"downsize": "0.0.8",
|
2016-07-19 19:04:34 +03:00
|
|
|
"express": "4.14.0",
|
2016-11-08 14:33:19 +03:00
|
|
|
"express-brute": "1.0.1",
|
2016-09-14 17:50:35 +03:00
|
|
|
"express-hbs": "1.0.3",
|
2016-09-14 20:13:36 +03:00
|
|
|
"extract-zip-fork": "1.5.1",
|
2016-11-07 13:50:04 +03:00
|
|
|
"fs-extra": "1.0.0",
|
2016-11-15 19:25:32 +03:00
|
|
|
"ghost-editor": "0.1.5",
|
2016-07-14 17:07:10 +03:00
|
|
|
"ghost-gql": "0.0.5",
|
2015-10-14 12:29:08 +03:00
|
|
|
"glob": "5.0.15",
|
2016-12-20 14:30:12 +03:00
|
|
|
"gscan": "0.2.0",
|
2016-06-30 20:46:21 +03:00
|
|
|
"html-to-text": "2.1.3",
|
✨ [FEATURE] AMP⚡ (#7229)
closes #6588, #7095
* `ImageObject` with image dimensions (#7152, #7151, #7153)
- Returns meta data as promise
- returns a new Promise from meta data
- uses `Promise.props()` to resolve `getClient()` and `getMetaData()`
- Adds 'image-size' util
The util returns an object like this
```
{
height: 50,
url: 'http://myblog.com/images/cat.jpg',
width: 50
};
```
if the dimensions can be fetched and rejects with error, if not.
In case we get a locally stored image or a not complete url (like `//www.gravatar.com/andsoon`), we add the protocol to the incomplete one and use `urlFor()` to get the absolute URL. If the request fails or `image-size` is not able to read the file, we reject with error.
- adds 'image-size' module to dependencies
- adds `getImageSizeFromUrl` function that returns image dimensions
- In preparation of AMP support and to improve our schema.org JSON-LD and structured data, I made the following changes:
- Changes the following properties to be `Objects`, which have a `url` property by default and a `dimensions` property, if `width` and `height` are available:
- `metaData.coverImage`
- `metaData.authorImage`
- `metaData.blog.logo`
- Checks cache by calling `getCachedImageSizeFromUrl`. If image dimensions were fetched already, returns them from cache instead of fetching them again.
- If we have image dimensions on hand, the output in our JSON-LD changes from normal urls to be full `ImageObjects`. Applies to all images and logos.
- Special case for `publisher.logo` as it has size restrictions: if the image doesn't fulfil the restrictions (<=600 width and <=60 height), we simply output the url instead, so like before.
- Adds new property for schema.org JSON-LD: `mainEntityOfPage` as an Object.
- Adds additional Open Graph data (if we have the image size): `og:image:width` and `og:image:height`
- Adds/updates tests
* AMP router and controller (#7171, #7157)
Implements AMP in `/apps/`:
- renders `amp.hbs` if route is `/:slug/amp/`
- updates `setResponseContext` to set context to `['amp', 'post']` for a amp post and `['amp', 'page']` for a page, but will not render amp template for a page
- updates `context_spec`
- registers 'amp' as new internal app
- adds the `amp.hbs` template to `core/server/apps/amp` which will be the default template for AMP posts.
- adds `isAmpURL` to `post-lookup`
* 🎨 Use `context` in meta as array (#7205)
Instead of reading the first value of the context array, we're checking if it includes certain context values.
This is a preparation change for AMP, where the context will be delivered as `['amp', 'post']`.
* ✨ AMP helpers (#7174, #7216, #7215, #7223)
- Adds AMP helpers `{{amp_content}}`, `{{amp_component}}` and `{{amp_ghost_head}}` to support AMP:
- `{{amp_content}}`:
- Adds `Amperize` as dependency
- AMP app uses new helper `{{amp_content}}` to render AMP HTML
- `Amperize` transforms regular HTML into AMP HTML
- Adds test for `{{amp_content}}` helper
- Adds 'Sanitize-HTML` as dependendy
- After the HTML get 'amperized' we still might have some HTML tags, which are prohibited in AMP HTML, so we use `sanitize-html` to remove those. With every update, `Amperize` gets and it is able to transform more HTML tags, they valid AMP HTML tags (e. g. `video` and `amp-video`) and will therefore not be removed.
- `{{amp_ghost_head}}`:
- registers `{{amp_ghost_head}}` helper, but uses `{{ghost_head}}` code
- uses `{{amp_ghost_head}}` in `amp.hbs` instead of `{{ghost_head}}`
- `{{ghost_head}}`:
- Render `amphtml` link in metadata for post, which links to the amp post (`getAmpUrl`)
- Updates all test in metadata to support `amp` context
- Changes context conditionals to work with full array instead of first array value
- Adds conditionals, so no additional javascript gets rendered in `{{ghost_head}}`
- Removes trailing `/amp/` in URLs, so only `amphtml` link on regular post renders it
- Adds a conditional, so no code injection will be included, for an `amp` context.
- `{{amp_components}}`:
- AMP app uses new helper `{{amp_components}}` to render necessary script tags for AMP extended components as `amp-iframe`, `amp-anime` and `amp-form`
- Adds test for `{{amp_components}}`
2016-08-22 19:49:27 +03:00
|
|
|
"image-size": "0.5.0",
|
2016-09-26 12:13:38 +03:00
|
|
|
"intl": "1.2.5",
|
2016-04-30 00:30:41 +03:00
|
|
|
"intl-messageformat": "1.3.0",
|
2017-01-04 14:34:44 +03:00
|
|
|
"jsonpath": "0.2.9",
|
2016-10-17 15:27:03 +03:00
|
|
|
"knex": "0.12.5",
|
2016-11-07 14:39:49 +03:00
|
|
|
"knex-migrator": "0.2.0",
|
2016-11-16 13:57:27 +03:00
|
|
|
"lodash": "4.17.2",
|
2016-09-26 16:23:49 +03:00
|
|
|
"mobiledoc-html-renderer": "0.3.0",
|
2017-01-04 14:42:51 +03:00
|
|
|
"moment": "2.17.1",
|
2016-11-06 19:59:40 +03:00
|
|
|
"moment-timezone": "0.5.9",
|
2016-08-06 11:30:30 +03:00
|
|
|
"multer": "1.2.0",
|
2016-11-08 16:47:14 +03:00
|
|
|
"mysql": "2.11.1",
|
2016-09-13 17:09:10 +03:00
|
|
|
"nconf": "0.8.4",
|
2016-10-03 17:42:34 +03:00
|
|
|
"netjet": "1.1.3",
|
2016-01-19 13:19:58 +03:00
|
|
|
"node-uuid": "1.4.7",
|
2015-05-06 02:54:23 +03:00
|
|
|
"nodemailer": "0.7.1",
|
2016-10-28 16:22:57 +03:00
|
|
|
"oauth2orize": "1.5.1",
|
2016-01-19 13:24:02 +03:00
|
|
|
"passport": "0.3.2",
|
2016-12-03 10:26:48 +03:00
|
|
|
"passport-ghost": "2.2.0",
|
2015-05-06 02:54:23 +03:00
|
|
|
"passport-http-bearer": "1.0.1",
|
|
|
|
|
"passport-oauth2-client-password": "0.1.2",
|
2016-04-21 12:44:58 +03:00
|
|
|
"path-match": "1.2.4",
|
2017-01-04 14:40:50 +03:00
|
|
|
"prettyjson": "1.2.1",
|
2016-01-19 13:52:25 +03:00
|
|
|
"rss": "1.2.1",
|
✨ [FEATURE] AMP⚡ (#7229)
closes #6588, #7095
* `ImageObject` with image dimensions (#7152, #7151, #7153)
- Returns meta data as promise
- returns a new Promise from meta data
- uses `Promise.props()` to resolve `getClient()` and `getMetaData()`
- Adds 'image-size' util
The util returns an object like this
```
{
height: 50,
url: 'http://myblog.com/images/cat.jpg',
width: 50
};
```
if the dimensions can be fetched and rejects with error, if not.
In case we get a locally stored image or a not complete url (like `//www.gravatar.com/andsoon`), we add the protocol to the incomplete one and use `urlFor()` to get the absolute URL. If the request fails or `image-size` is not able to read the file, we reject with error.
- adds 'image-size' module to dependencies
- adds `getImageSizeFromUrl` function that returns image dimensions
- In preparation of AMP support and to improve our schema.org JSON-LD and structured data, I made the following changes:
- Changes the following properties to be `Objects`, which have a `url` property by default and a `dimensions` property, if `width` and `height` are available:
- `metaData.coverImage`
- `metaData.authorImage`
- `metaData.blog.logo`
- Checks cache by calling `getCachedImageSizeFromUrl`. If image dimensions were fetched already, returns them from cache instead of fetching them again.
- If we have image dimensions on hand, the output in our JSON-LD changes from normal urls to be full `ImageObjects`. Applies to all images and logos.
- Special case for `publisher.logo` as it has size restrictions: if the image doesn't fulfil the restrictions (<=600 width and <=60 height), we simply output the url instead, so like before.
- Adds new property for schema.org JSON-LD: `mainEntityOfPage` as an Object.
- Adds additional Open Graph data (if we have the image size): `og:image:width` and `og:image:height`
- Adds/updates tests
* AMP router and controller (#7171, #7157)
Implements AMP in `/apps/`:
- renders `amp.hbs` if route is `/:slug/amp/`
- updates `setResponseContext` to set context to `['amp', 'post']` for a amp post and `['amp', 'page']` for a page, but will not render amp template for a page
- updates `context_spec`
- registers 'amp' as new internal app
- adds the `amp.hbs` template to `core/server/apps/amp` which will be the default template for AMP posts.
- adds `isAmpURL` to `post-lookup`
* 🎨 Use `context` in meta as array (#7205)
Instead of reading the first value of the context array, we're checking if it includes certain context values.
This is a preparation change for AMP, where the context will be delivered as `['amp', 'post']`.
* ✨ AMP helpers (#7174, #7216, #7215, #7223)
- Adds AMP helpers `{{amp_content}}`, `{{amp_component}}` and `{{amp_ghost_head}}` to support AMP:
- `{{amp_content}}`:
- Adds `Amperize` as dependency
- AMP app uses new helper `{{amp_content}}` to render AMP HTML
- `Amperize` transforms regular HTML into AMP HTML
- Adds test for `{{amp_content}}` helper
- Adds 'Sanitize-HTML` as dependendy
- After the HTML get 'amperized' we still might have some HTML tags, which are prohibited in AMP HTML, so we use `sanitize-html` to remove those. With every update, `Amperize` gets and it is able to transform more HTML tags, they valid AMP HTML tags (e. g. `video` and `amp-video`) and will therefore not be removed.
- `{{amp_ghost_head}}`:
- registers `{{amp_ghost_head}}` helper, but uses `{{ghost_head}}` code
- uses `{{amp_ghost_head}}` in `amp.hbs` instead of `{{ghost_head}}`
- `{{ghost_head}}`:
- Render `amphtml` link in metadata for post, which links to the amp post (`getAmpUrl`)
- Updates all test in metadata to support `amp` context
- Changes context conditionals to work with full array instead of first array value
- Adds conditionals, so no additional javascript gets rendered in `{{ghost_head}}`
- Removes trailing `/amp/` in URLs, so only `amphtml` link on regular post renders it
- Adds a conditional, so no code injection will be included, for an `amp` context.
- `{{amp_components}}`:
- AMP app uses new helper `{{amp_components}}` to render necessary script tags for AMP extended components as `amp-iframe`, `amp-anime` and `amp-form`
- Adds test for `{{amp_components}}`
2016-08-22 19:49:27 +03:00
|
|
|
"sanitize-html": "1.13.0",
|
2016-07-15 14:07:07 +03:00
|
|
|
"semver": "5.3.0",
|
2015-05-06 02:54:23 +03:00
|
|
|
"showdown-ghost": "0.3.6",
|
2016-09-23 14:58:11 +03:00
|
|
|
"superagent": "2.3.0",
|
2015-12-08 14:01:49 +03:00
|
|
|
"unidecode": "0.1.8",
|
2016-09-19 15:51:36 +03:00
|
|
|
"validator": "5.7.0",
|
2016-02-09 00:30:57 +03:00
|
|
|
"xml": "1.0.1"
|
2015-05-06 02:54:23 +03:00
|
|
|
},
|
|
|
|
|
"optionalDependencies": {
|
2016-11-08 16:47:14 +03:00
|
|
|
"sqlite3": "3.1.8"
|
2015-05-06 02:54:23 +03:00
|
|
|
},
|
|
|
|
|
"devDependencies": {
|
2016-04-06 23:07:55 +03:00
|
|
|
"grunt": "1.0.1",
|
|
|
|
|
"grunt-bg-shell": "2.3.3",
|
|
|
|
|
"grunt-cli": "1.2.0",
|
|
|
|
|
"grunt-contrib-clean": "1.0.0",
|
2016-05-24 20:53:54 +03:00
|
|
|
"grunt-contrib-compress": "1.3.0",
|
2016-04-06 23:07:55 +03:00
|
|
|
"grunt-contrib-copy": "1.0.0",
|
|
|
|
|
"grunt-contrib-jshint": "1.0.0",
|
2016-07-19 19:04:20 +03:00
|
|
|
"grunt-contrib-uglify": "2.0.0",
|
2016-04-06 23:07:55 +03:00
|
|
|
"grunt-contrib-watch": "1.0.0",
|
|
|
|
|
"grunt-docker": "0.0.11",
|
|
|
|
|
"grunt-express-server": "0.5.3",
|
2016-06-22 00:22:16 +03:00
|
|
|
"grunt-jscs": "3.0.1",
|
2016-04-06 23:07:55 +03:00
|
|
|
"grunt-mocha-cli": "2.1.0",
|
2016-08-10 21:09:59 +03:00
|
|
|
"grunt-mocha-istanbul": "5.0.2",
|
2016-08-13 15:39:42 +03:00
|
|
|
"grunt-shell": "1.3.1",
|
2016-05-31 16:38:11 +03:00
|
|
|
"grunt-subgrunt": "1.2.0",
|
2015-05-28 18:16:09 +03:00
|
|
|
"grunt-update-submodules": "0.4.1",
|
2016-09-20 13:52:16 +03:00
|
|
|
"gulp": "3.9.1",
|
2016-09-26 19:17:40 +03:00
|
|
|
"gulp-git-submodule": "1.0.1",
|
2016-10-03 17:08:40 +03:00
|
|
|
"gulp-help": "1.6.1",
|
2016-10-03 11:30:22 +03:00
|
|
|
"gulp-jscs": "4.0.0",
|
2016-11-15 19:27:38 +03:00
|
|
|
"gulp-jshint": "2.0.3",
|
2016-10-03 11:30:22 +03:00
|
|
|
"gulp-jsonlint": "1.1.2",
|
2016-09-20 13:52:16 +03:00
|
|
|
"gulp-livereload": "3.8.1",
|
2016-10-07 20:22:04 +03:00
|
|
|
"gulp-nodemon": "2.2.1",
|
🛠 Improve existing gulp tasks (#7444)
refs #7427
- Deleting the `built` or `dist` directory doesn't result in an error, when running `gulp dev`
- Adds default task as `gulp dev`
- Adds abbreviations for the repositories in `gulp setup` task (`--ghost` -> `-g`, `--admin` -> `-a` and `--casper` -> `-c`) to type less 😊
- Installs dependencies on `gulp dev`, if called with `--deps` or `-d`
- Sets `verbose` option nodemon to default (=`false`) to have less unneccessary logging.
- Will do a delete of all dependencies and install them again ('FFS'), if `gulp deps` is called with a force flag.
- Will update submodules not matter what, if `gulp submodules` is called with a force flag. Calling `gulp submodules` without the force flag will only update/initiate the submodules, if the folders don't exist.
- Better logging messages and sequential task handling.
- Removes `gulp-shell` as dependency, as this is on gulp's blacklist
- Refactors code, that used `gulp-shell` to use `child_process.exec` or `spawn` instead.
- Exits properly if node crashes
-----------------------
Tasks available after this PR:
- `gulp server`: Starts a nodemon server with livereload of the ghost core only. No client build here.
- `gulp dev`: [ --deps | -d ] Starts development mode for Ghost, incl. client build and livereload for both. Will also update the submodules if the directories are missing. If called with with `--deps` flag, it will install client and core dependencies.
- `gulp submodules`: [ --force | -f ] Will update the submodules, if directories are missing. Will update no matter what, if called with force flag.
- `gulp deps`: [ --force | -f ] Will update client and core dependencies. Does a fresh install of both (delete, cache clear and install) if called with force flag.
- `gulp setup`: </br>[ --ghost | -g 'branch' or 'pr/1234' ]
[ --admin | -a 'branch' or 'pr/1234' ]
[ --casper | -c 'branch' or 'pr/1234' ]
[ --force | -f ]
Takes various - optional - parameters. If called without parameters, this task will update submodules first (if directory doesn't exist) and then install client and core dependendies.
If called with branch 'master', submodules will be updated.
Calling with the force flag will do a clean install of the dependencies.
There's no autocomplete for branchnames at the moment 😔
To check out a PR (e. g. `--ghost pr/7444`), it is necessary, that you add an additional fetch line in the `.git/config` file for each repository: `fetch = +refs/pull/*/head:refs/remotes/upstream/pr/*`. See https://dev.ghost.org/easy-git-pr-test/ for further information.
2016-09-29 20:32:17 +03:00
|
|
|
"gulp-util": "3.0.7",
|
2016-09-19 15:51:25 +03:00
|
|
|
"istanbul": "0.4.5",
|
2016-10-28 16:22:10 +03:00
|
|
|
"jshint": "2.9.4",
|
2016-10-03 11:30:22 +03:00
|
|
|
"jshint-stylish": "2.2.1",
|
2016-04-30 00:30:41 +03:00
|
|
|
"matchdep": "1.0.1",
|
2016-09-26 19:17:40 +03:00
|
|
|
"minimist": "1.2.0",
|
2016-12-25 23:07:43 +03:00
|
|
|
"mocha": "3.2.0",
|
2016-10-28 16:26:27 +03:00
|
|
|
"nock": "8.2.1",
|
2016-07-05 19:25:23 +03:00
|
|
|
"rewire": "2.5.2",
|
2016-09-26 19:17:40 +03:00
|
|
|
"run-sequence": "1.2.2",
|
2017-01-04 14:44:42 +03:00
|
|
|
"should": "11.1.2",
|
2016-02-08 00:27:01 +03:00
|
|
|
"should-http": "0.0.4",
|
2016-09-19 16:42:22 +03:00
|
|
|
"sinon": "1.17.6",
|
2016-10-25 14:19:46 +03:00
|
|
|
"supertest": "2.0.1",
|
2017-01-04 14:30:17 +03:00
|
|
|
"tmp": "0.0.31"
|
2016-02-07 16:16:18 +03:00
|
|
|
},
|
|
|
|
|
"greenkeeper": {
|
2016-03-29 06:24:32 +03:00
|
|
|
"ignore": [
|
2016-10-27 14:41:32 +03:00
|
|
|
"bunyan",
|
2016-03-29 06:24:32 +03:00
|
|
|
"glob",
|
|
|
|
|
"mysql",
|
|
|
|
|
"nodemailer",
|
2016-09-30 15:38:14 +03:00
|
|
|
"showdown-ghost",
|
|
|
|
|
"grunt",
|
|
|
|
|
"grunt-bg-shell",
|
|
|
|
|
"grunt-cli",
|
|
|
|
|
"grunt-contrib-clean",
|
|
|
|
|
"grunt-contrib-compress",
|
|
|
|
|
"grunt-contrib-copy",
|
|
|
|
|
"grunt-contrib-jshint",
|
|
|
|
|
"grunt-contrib-uglify",
|
|
|
|
|
"grunt-contrib-watch",
|
|
|
|
|
"grunt-docker",
|
|
|
|
|
"grunt-express-server",
|
|
|
|
|
"grunt-jscs",
|
|
|
|
|
"grunt-mocha-cli",
|
|
|
|
|
"grunt-mocha-istanbul",
|
|
|
|
|
"grunt-shell",
|
|
|
|
|
"grunt-subgrunt",
|
|
|
|
|
"grunt-update-submodules"
|
2016-03-29 06:24:32 +03:00
|
|
|
]
|
2015-05-06 02:54:23 +03:00
|
|
|
}
|
2014-02-09 19:29:23 +04:00
|
|
|
}
|
