The best React-based framework with performance, scalability and security built in.
MIT License
Published by KyleAMathews about 7 years ago
Exciting to see the first source plugin for a database added!
Published by KyleAMathews about 7 years ago
modifyWebpackConfig
docs #1613 @KyleAMathewsPublished by KyleAMathews over 7 years ago
Published by KyleAMathews over 7 years ago
A few more days, another minor release π
Highlight of this release is @felixjung adding support for hot reloading changes to site's html.js during development in #1473
Beyond that, lots of bug fixes and small feature additions from the community!
Published by KyleAMathews over 7 years ago
Continuing our blistering development pace, in the five days since our initial 1.0.0 release there's been 44 merged PRs by 20 different authors. Thanks everyone!
gatsby-plugin-emotion
#1447 @rawrmonstarowner
assignation to prevent error #1454 @sebastienfiPublished by KyleAMathews over 7 years ago
Release blog post at https://www.gatsbyjs.org/blog/gatsby-v1/
Published by KyleAMathews over 7 years ago
Perhaps/hopefully the last beta before 1.0.0!
Published by KyleAMathews over 7 years ago
Our versions of GraphQL got mis-matched due to the new release of Relay Compiler so quick new release to fix that.
Published by KyleAMathews over 7 years ago
Published by KyleAMathews over 7 years ago
Published by KyleAMathews over 7 years ago
Quick release with some bug fixing
Published by KyleAMathews over 7 years ago
Thanks so much to everyone who's helped get Gatsby to this point. Now onto 1.0.
linkPrefix
to pathPrefix
and add an example site #1155 @kyleamathewsPublished by KyleAMathews over 7 years ago
html.js
component #1107 @kyleamathewsgatsby-config.js
is no longer required #1107 @kyleamathewsserve-build
command is now just serve
#1107 @kyleamathewsPublished by KyleAMathews over 7 years ago
API changes:
upsertPage
is now createPage
addFieldToNode
is now createNodeField
deletePageByPath
is now deletePage
addNodeToParent
is now createParentChildLink
clientEntry
is now onClientEntry
onNodeCreate
is now onCreateNode
onUpsertPage
is now onCreatePage
extendNodeType
is now setFieldsOnGraphQLNodeType
modifyHeadComponents
and modifyPostBodyComponents
were removed in favor of aonRenderBody
.replaceServerBodyRender
is now replaceRenderer
Published by KyleAMathews over 7 years ago
updateNode
action creator as part of making nodes immutable in #1035.addFieldToNode
for adding fields to nodes createdaddNodeToParent
for adding a new node as a child toPublished by KyleAMathews over 7 years ago
toFormat
argument to the ImageSharp GraphQL type so can changepng
to jpg
.node.type
and others will need changed tonode.internal.type
#960<div>
used by Gatsby to mount React to ___gatsby
layouts/index.js
not layouts/default.js
https://github.com/gatsbyjs/gatsby/pull/940#issuecomment-300537162
this.props.children
in layout components is now a function https://github.com/gatsbyjs/gatsby/pull/940#issuecomment-300878300
/___graphql
Published by KyleAMathews over 7 years ago
package.json
and gatsby-config.js
need to beexport const pageQuery = `
{
allMarkdownMark {
edges {
node {
id
}
}
}
}
`
You must now write:
export const pageQuery = graphql`
query IndexQuery {
allMarkdownMark {
edges {
node {
id
}
}
}
}
`
Published by KyleAMathews over 7 years ago
Gatsby v1's data layer is starting to feel quite solid.
For this latest alpha, I did a almost complete refactor of the data layer adding in Redux and ideas from event sourcing and modern build tools like Buck and Bazel from Facebook and Google respectively.
Now all data processing is incremental and completely cached. On booting, Gatsby looks at your data contents to decide if new processing is needed and only processes data that's actually changed. One large site built on 1.0 saw it's bootstrap time drop from nearly a minute to under 5 seconds!
And as part of this work, Gatsby's data system now automatically watches all your data sources for changes and reprocesses data on the fly. Remote or local data, if you change it, the change will be automatically pushed to the development version of your site. This is handy for editing a local markdown file but also a gatsby plugin can be monitoring a remote API for changes and automatically pull down data and update your site when something is updated.
Imagine a small team working on a site with a developer and two people working on content hosted on a CMS. Every time content is updated, the developer sees the changes in near real-time on the development site.
This was the last big piece blocking 1.0.0 from being released. There are a number of smaller tasks to complete but these should be more predictable in scope. There's plenty of smaller tasks to do! Please come help out!
/src
subdirectory https://github.com/gatsbyjs/gatsby/pull/802
parse
plugins to transformer
https://github.com/gatsbyjs/gatsby/pull/818
Published by KyleAMathews over 7 years ago
@NMinhNguyen added this very nice PR adding support for named exports to JS frontmatter https://github.com/gatsbyjs/gatsby/pull/838
So this is now supported:
export const data = {
titles: ['My title', 'My other title'],
}
Published by KyleAMathews over 7 years ago
eval
source-maps technique for cheap-module-source-maps
.