Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(gatsby): fix domready package to be compatible with ie10 #13027

Merged
merged 3 commits into from
Apr 2, 2019
Merged

chore(gatsby): fix domready package to be compatible with ie10 #13027

merged 3 commits into from
Apr 2, 2019

Conversation

mikaelkristiansson
Copy link
Contributor

Description

When a gatsby site is loaded in internet explorer 10 it will not render.
Since gatsby use package domready (not maintained since 4 years back) I decided to fork it and fix the problem.

this is how gatsby call the function:

domReady(() => {
      renderer(
        <NewRoot />,
        typeof window !== `undefined`
          ? document.getElementById(`___gatsby`)
          : void 0,
        () => {
          postInitialRenderWork()
          apiRunner(`onInitialClientRender`)
        }
      )
    })

but since domready isn't working correct in ie10 the renderer function won't be called.

The problem causing this in domready package was it calls

document.documentElement.doScroll

in ie10 this returns as a function, so I had to change it to call the function to get the value expected:

ie10 ? document.documentElement.doScroll() : document.documentElement.doScroll

link to package and git repo:
https://www.npmjs.com/package/domready-loaded
https://github.com/mikaelkristiansson/domready

Related Issues

Fixes this issue: #11604

@mikaelkristiansson mikaelkristiansson requested a review from a team as a code owner April 2, 2019 10:44
@wardpeet
Copy link
Contributor

wardpeet commented Apr 2, 2019

why wouldn't you publish it on your own name @mikaelkristiansson/domready? Also you should create a PR for this on his repo so we can switch back to domready later on.

Another approach is just doing it ourselves XD For ie9+ we don't need any doScroll hacks.

function domReady(cb => {
  if (!document) {return}
  if (document.readyState === 'complete') {
    return cb()
  }

  document.addEventListener('DOMContentLoaded', function listener() {
    document.removeEventListener('DOMContentLoaded', listener);
    cb()
  })
});

@mikaelkristiansson
Copy link
Contributor Author

I've created a PR to the original repo:
ded/domready#59
and also updated package to use @mikaelkristiansson/domready

@wardpeet
Copy link
Contributor

wardpeet commented Apr 2, 2019

thanks! Let me also explain why @mikaelkristiansson/domready is valuable for us instead of domready-loaded. This mostly indicated that this is a temp package derived from domready. With domready-loaded we have to open your github to see that it's a fork, ...

@mikaelkristiansson mikaelkristiansson changed the title changed domready package to domready-loaded which is compatible with ie10 changed domready package to be compatible with ie10 Apr 2, 2019
Copy link
Contributor

@wardpeet wardpeet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@wardpeet wardpeet changed the title changed domready package to be compatible with ie10 chore(garsby): fix domready package to be compatible with ie10 Apr 2, 2019
@wardpeet wardpeet changed the title chore(garsby): fix domready package to be compatible with ie10 chore(gatsby): fix domready package to be compatible with ie10 Apr 2, 2019
@wardpeet wardpeet merged commit 6a221c2 into gatsbyjs:master Apr 2, 2019
@gatsbot
Copy link

gatsbot bot commented Apr 2, 2019

Holy buckets, @mikaelkristiansson — we just merged your PR to Gatsby! 💪💜

Gatsby is built by awesome people like you. Let us say “thanks” in two ways:

  1. We’d like to send you some Gatsby swag. As a token of our appreciation, you can go to the Gatsby Swag Store and log in with your GitHub account to get a coupon code good for one free piece of swag. (Currently we’ve got a couple t-shirts available, plus some socks that are really razzing our berries right now.)
  2. We just invited you to join the Gatsby organization on GitHub. This will add you to our team of maintainers. Accept the invite by visiting https://github.com/orgs/gatsbyjs/invitation. By joining the team, you’ll be able to label issues, review pull requests, and merge approved pull requests.

If there’s anything we can do to help, please don’t hesitate to reach out to us: tweet at @gatsbyjs and we’ll come a-runnin’.

Thanks again!

dhurlburtusa added a commit that referenced this pull request Apr 3, 2019
* docs(gatsby-source-shopify): Add note about API permissions (#13037)

Note which permissions you should enable on the Shopify Storefront API. Without these permissions you'll get a fairly cryptic error message.

* chore(docs): match the Wording Style of Other Tutorial Parts (#13034)

* chore(docs): fix typo in convincing others doc (#13033)

<!--
  Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or
  ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->

## Description

Fixes a misspelled word.

* fix(docs): expand guidelist on partnering with gatsby page (#13029)

Following up on #12970. Current https://www.gatsbyjs.org/docs/partnering-with-gatsby/:

![image](https://user-images.githubusercontent.com/21834/55404445-2f445080-5558-11e9-84d8-f75db8dd7297.png)

* fix(starters): update gatsby monorepo (#12925)

This PR contains the following updates:

| Package | Type | Update | Change | References |
|---|---|---|---|---|
| gatsby | dependencies | patch | [`^2.3.3` -> `^2.3.5`](https://diff.intrinsic.com/gatsby/2.3.3/2.3.5) | [source](https://togithub.com/gatsbyjs/gatsby) |
| gatsby-image | dependencies | patch | [`^2.0.35` -> `^2.0.37`](https://diff.intrinsic.com/gatsby-image/2.0.35/2.0.37) | [source](https://togithub.com/gatsbyjs/gatsby) |
| gatsby-plugin-manifest | dependencies | patch | [`^2.0.25` -> `^2.0.26`](https://diff.intrinsic.com/gatsby-plugin-manifest/2.0.25/2.0.26) | [source](https://togithub.com/gatsbyjs/gatsby) |

---

### Release Notes

<details>
<summary>gatsbyjs/gatsby</summary>

### [`v2.3.5`](https://togithub.com/gatsbyjs/gatsby/compare/[email protected]@2.3.5)

[Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/[email protected]@2.3.5)

### [`v2.3.4`](https://togithub.com/gatsbyjs/gatsby/compare/[email protected]@2.3.4)

[Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/[email protected]@2.3.4)

</details>

---

### Renovate configuration

:date: **Schedule**: At any time (no schedule defined).

:vertical_traffic_light: **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

:recycle: **Rebasing**: Whenever PR becomes conflicted, or if you modify the PR title to begin with "`rebase!`".

:ghost: **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/config-help/issues) if that's undesired.

---

 - [ ] <!-- renovate-rebase -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Renovate Bot](https://togithub.com/marketplace/renovate). View repository job log [here](https://renovatebot.com/dashboard#gatsbyjs/gatsby).

* feat(blog): add gatsby is great blog post (#12777)

* chore: add blog post

* chore: keep iterating

* chore: more tweaks

* feat: nearly finish up

* chore: run tinypng

* chore: fix some typos

* chore: fix snippet

* chore: add a gif, it gets the people going

* chore: more

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* chore: change date

* chore: tighten up last section

* chore: change data

* chore: update per feedback

* chore(docs): replace absolute links with relative links (#12949)


<!--
  Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or
  ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->

## Description

Suggest a more complete structure to the example gatsby-config.js file

## Related Issues

Along with #12103 this PR fixes #11957

<!--
  Link to the issue that is fixed by this PR (if there is one)
  e.g. Fixes #1234, Addresses #1234, Related to #1234, etc.
-->

* chore(showcase): Add Assortment to site showcase (#13002)

## Description

Adding [assortment.io](https://assortment.io) to site showcase. Assortment is my Web Development blog that I've recently updated to Gatsby, Netlify, Netlify CMS and Emotion. It'd be cool to see it on the showcase 😃

* feat(gatsby-dev-cli): add verdaccio support (#11525)

* feat(gatsby-dev-cli): add verdaccio support [wip]

* yuck - don't look

* just to verify verdaccio

* fix gitignore and add htpasswd with dummy gatsby-dev user

* some logging to understand why it tries to handle all the packages

* just temporarily so it hopefully at least works

* moar data

* don't copy all the packages right now

* don't rely on package name starting with "gatsby" heuristic

* tmp commit

* tmp

* fs change

* tmp

* a

* updates

* remove random files that shouldn't be here

* tmp

* revert dep changes

* ignore changes to package.json created during publishing

* testing of dep change in gatsby-cli is picked up by gatsby-dev-cli

* let's see if gatsby-dev will handle case of no node_modules

* sanity check

* adjust console message

* add missing devDeps

* more missing devDeps

* grab package.json from unpkg if package is not yet installed locally

* correctly ignore package.json changes during publishing

* cleaning things up

* htpasswd loc

* restore gatsby package.json

* adjust ignore files

* gatsby-dev-cli: ignore tests

* remove extra ln

* less console output

* turns out you don't need htpasswd after all

* use exact when installing local packages  - timestamp is used in version

* why it failed?

* use yarn for publishing - see verdaccio/verdaccio#997

* v0.1.1

* add temporary .npmrc file to allow anonymous publishes

* add some jsdocs

* update yarn.lock

* oops

* debug why still can't publish anon

* adjust npmrc content

* doh

* Revert "debug why still can't publish anon"

This reverts commit fc1045a.

* handle package installation of deps didn't change

* skip version changes for packages in gatsby mono-repo, queue copying instead of doing it immediately

* fix tests

* packages stored in verdaccio storage seems to be picked up by jest and causing trouble, so let's ignore verdaccio storage directory

* bye "wat", you will be missed

* bail early to avoid conditional bracket hell

* more bailing early

* more concise

* new line

* use exaca to simplify running yarn

* clean up www/.gitignore

* handle not existing packages

* remove unused (was needed for basic auth)

* cleanup temp file changes when process exit in middle of publishing

* ops

* Apply suggestions from code review

Co-Authored-By: pieh <[email protected]>

* cleanup unpkg response handler

* move stuff around

* remove tmp comment

* document traversePackageDocs fn

* restrcuture files

* add basic tests for traversingPackageDeps

* add basic tests for generating packages to publish (based on dep graph)

* fix tests on windows

* handle circular dependencies when constructing list of packages to publish

* remove cat ;(

* restore original e2e-test script

* update gitignore

* chore(release): Publish

 - [email protected]
 - [email protected]
 - [email protected]
 - [email protected]
 - [email protected]
 - [email protected]

* chore(release): Publish

 - [email protected]

* docs(gatsby-dev-cli): Edit README (#13049)

* Build out Gatsby media information in docs (#12906)

* add video info, delete unnecessary stubs

Related to #12903

* fix internal link for html5 video section

* update videoTitle example

Co-Authored-By: marcysutton <[email protected]>

* Apply suggestions from code review

thanks for the feedback!

Co-Authored-By: marcysutton <[email protected]>

* incorporate feedback, make into real docs!!

* delete unused stubs

* Update docs/docs/working-with-video.md

Co-Authored-By: marcysutton <[email protected]>

* Update docs/docs/working-with-video.md

Co-Authored-By: marcysutton <[email protected]>

* chore(gatsby): fix domready package to be compatible with ie10 (#13027)

* changed domready package to domready-loaded which is compatible with ie10

* updated domready to @mikaelkristiansson/domready

* updated packages/gatsby to use @mikaelkristiansson/domready

* chore(release): Publish

 - [email protected]

* feat(gatsby-transformer-react-docgen): use local babel config for react-docgen (#12001)

* feat: use local babel config for react-docgen

BREAKING CHANGE: now uses the local babel config with a fallback

* Update README.md

* chore(release): Publish

 - [email protected]

* chore(docs): add “Why I used GatsbyJS (#12954)

Why I used GatsbyJS

<!--
  Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or
  ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->

## Description

<!-- Write a brief description of the changes introduced by this PR -->

## Related Issues

<!--
  Link to the issue that is fixed by this PR (if there is one)
  e.g. Fixes #1234, Addresses #1234, Related to #1234, etc.
-->

* feat(www): don't check for overview frontmatter (#13060)

Fixes `[[guidelist]]` not being replaced in few pages (i.e. in https://www.gatsbyjs.org/docs/winning-over-stakeholders/ )

The code is handling cases when there are no children (tried building locally and it worked just fine).

Follow up to this would be to clear `.md` files that use `overview` and adjust page query. But this is just quick fix.

* chore(docs): add starter library to docs sidebar under starters (#12963)

 40% of people visiting the starters page go here next, so we should probably add this:

![image](https://user-images.githubusercontent.com/4388699/55285012-58d26180-5337-11e9-9259-68e81b4894ad.png)

* chore(showcase): Add gmartinez.dev to showcase (#13067)

<!--
  Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or
  ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->

## Description

Adding gmartinez.dev to showcase list in site.yml

<!--
  Link to the issue that is fixed by this PR (if there is one)
  e.g. Fixes #1234, Addresses #1234, Related to #1234, etc.
-->


Co-authored-by: Lennart <[email protected]>

* fix(gatsby): don't try to statically analyze gatsby-node, require it and examine exports instead (#13053)

* fix: don't try to statically analyze gatsby-node, require it and examine exports instead

* differentiate test names

* Update packages/gatsby/src/bootstrap/resolve-module-exports.js

Co-Authored-By: pieh <[email protected]>

* chore(release): Publish

 - [email protected]

* Use Loki's elemMatch operator (#13025)

* feat(gatsby): add util.promisify polyfill for older node version (#13024)

* refactor(gatsby): gatsby develop: cleanup port detection (#13006)

* chore(release): Publish

 - [email protected]

* fix(gatsby): ignore __esModule export in gatsby-node exports (#13081)

I introduced bug/regression in #13053 by not removing `__esModule` export name from resolved export names - it break some plugins

Fixes: #13079

* chore(release): Publish

 - [email protected]

* fix(www): Hubspot form UI (#13080)

* fix(www): Work around HubSpot’s CSS being loaded

…by pulling in react-hubspot-form locally, and modifying it slightly. See comment in `www/src/components/react-hubspot-form` for more info.

* Fix `formInput` styles

… now matching the reference homepage newsletter form — no more Futura PT for input text.

* Return nothing because linter

* Make into Two Words
DSchau pushed a commit that referenced this pull request Apr 4, 2019
* Fix Comma Usage

* Fix Comma Usage; Misc Improvements (#13038)

* Fix Misuse of Commas, Et Al (#13039)

Use em dash in place of two hyphens.
Format paragraph to be on one line (apparently the convention).

* Fix Comma Usage and Do Some Misc Changes (#13040)

* Fix Comma Usage and Do Some Misc Changes

Do code formatting to match rest of file.
Use em dash instead of two hyphens.
Etc.

* Update HTML Entity

* Add Hyphen for Clarity (#13042)

* Fix Comma Usage in Blog (#13085)

* docs(gatsby-source-shopify): Add note about API permissions (#13037)

Note which permissions you should enable on the Shopify Storefront API. Without these permissions you'll get a fairly cryptic error message.

* chore(docs): match the Wording Style of Other Tutorial Parts (#13034)

* chore(docs): fix typo in convincing others doc (#13033)

<!--
  Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or
  ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->

## Description

Fixes a misspelled word.

* fix(docs): expand guidelist on partnering with gatsby page (#13029)

Following up on #12970. Current https://www.gatsbyjs.org/docs/partnering-with-gatsby/:

![image](https://user-images.githubusercontent.com/21834/55404445-2f445080-5558-11e9-84d8-f75db8dd7297.png)

* fix(starters): update gatsby monorepo (#12925)

This PR contains the following updates:

| Package | Type | Update | Change | References |
|---|---|---|---|---|
| gatsby | dependencies | patch | [`^2.3.3` -> `^2.3.5`](https://diff.intrinsic.com/gatsby/2.3.3/2.3.5) | [source](https://togithub.com/gatsbyjs/gatsby) |
| gatsby-image | dependencies | patch | [`^2.0.35` -> `^2.0.37`](https://diff.intrinsic.com/gatsby-image/2.0.35/2.0.37) | [source](https://togithub.com/gatsbyjs/gatsby) |
| gatsby-plugin-manifest | dependencies | patch | [`^2.0.25` -> `^2.0.26`](https://diff.intrinsic.com/gatsby-plugin-manifest/2.0.25/2.0.26) | [source](https://togithub.com/gatsbyjs/gatsby) |

---

### Release Notes

<details>
<summary>gatsbyjs/gatsby</summary>

### [`v2.3.5`](https://togithub.com/gatsbyjs/gatsby/compare/[email protected]@2.3.5)

[Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/[email protected]@2.3.5)

### [`v2.3.4`](https://togithub.com/gatsbyjs/gatsby/compare/[email protected]@2.3.4)

[Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/[email protected]@2.3.4)

</details>

---

### Renovate configuration

:date: **Schedule**: At any time (no schedule defined).

:vertical_traffic_light: **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

:recycle: **Rebasing**: Whenever PR becomes conflicted, or if you modify the PR title to begin with "`rebase!`".

:ghost: **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/config-help/issues) if that's undesired.

---

 - [ ] <!-- renovate-rebase -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Renovate Bot](https://togithub.com/marketplace/renovate). View repository job log [here](https://renovatebot.com/dashboard#gatsbyjs/gatsby).

* feat(blog): add gatsby is great blog post (#12777)

* chore: add blog post

* chore: keep iterating

* chore: more tweaks

* feat: nearly finish up

* chore: run tinypng

* chore: fix some typos

* chore: fix snippet

* chore: add a gif, it gets the people going

* chore: more

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* chore: change date

* chore: tighten up last section

* chore: change data

* chore: update per feedback

* chore(docs): replace absolute links with relative links (#12949)


<!--
  Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or
  ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->

## Description

Suggest a more complete structure to the example gatsby-config.js file

## Related Issues

Along with #12103 this PR fixes #11957

<!--
  Link to the issue that is fixed by this PR (if there is one)
  e.g. Fixes #1234, Addresses #1234, Related to #1234, etc.
-->

* chore(showcase): Add Assortment to site showcase (#13002)

## Description

Adding [assortment.io](https://assortment.io) to site showcase. Assortment is my Web Development blog that I've recently updated to Gatsby, Netlify, Netlify CMS and Emotion. It'd be cool to see it on the showcase 😃

* Fix Comma Usage; Misc Updates

* Make into Two Words (#13084)

* docs(gatsby-source-shopify): Add note about API permissions (#13037)

Note which permissions you should enable on the Shopify Storefront API. Without these permissions you'll get a fairly cryptic error message.

* chore(docs): match the Wording Style of Other Tutorial Parts (#13034)

* chore(docs): fix typo in convincing others doc (#13033)

<!--
  Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or
  ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->

## Description

Fixes a misspelled word.

* fix(docs): expand guidelist on partnering with gatsby page (#13029)

Following up on #12970. Current https://www.gatsbyjs.org/docs/partnering-with-gatsby/:

![image](https://user-images.githubusercontent.com/21834/55404445-2f445080-5558-11e9-84d8-f75db8dd7297.png)

* fix(starters): update gatsby monorepo (#12925)

This PR contains the following updates:

| Package | Type | Update | Change | References |
|---|---|---|---|---|
| gatsby | dependencies | patch | [`^2.3.3` -> `^2.3.5`](https://diff.intrinsic.com/gatsby/2.3.3/2.3.5) | [source](https://togithub.com/gatsbyjs/gatsby) |
| gatsby-image | dependencies | patch | [`^2.0.35` -> `^2.0.37`](https://diff.intrinsic.com/gatsby-image/2.0.35/2.0.37) | [source](https://togithub.com/gatsbyjs/gatsby) |
| gatsby-plugin-manifest | dependencies | patch | [`^2.0.25` -> `^2.0.26`](https://diff.intrinsic.com/gatsby-plugin-manifest/2.0.25/2.0.26) | [source](https://togithub.com/gatsbyjs/gatsby) |

---

### Release Notes

<details>
<summary>gatsbyjs/gatsby</summary>

### [`v2.3.5`](https://togithub.com/gatsbyjs/gatsby/compare/[email protected]@2.3.5)

[Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/[email protected]@2.3.5)

### [`v2.3.4`](https://togithub.com/gatsbyjs/gatsby/compare/[email protected]@2.3.4)

[Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/[email protected]@2.3.4)

</details>

---

### Renovate configuration

:date: **Schedule**: At any time (no schedule defined).

:vertical_traffic_light: **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

:recycle: **Rebasing**: Whenever PR becomes conflicted, or if you modify the PR title to begin with "`rebase!`".

:ghost: **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/config-help/issues) if that's undesired.

---

 - [ ] <!-- renovate-rebase -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Renovate Bot](https://togithub.com/marketplace/renovate). View repository job log [here](https://renovatebot.com/dashboard#gatsbyjs/gatsby).

* feat(blog): add gatsby is great blog post (#12777)

* chore: add blog post

* chore: keep iterating

* chore: more tweaks

* feat: nearly finish up

* chore: run tinypng

* chore: fix some typos

* chore: fix snippet

* chore: add a gif, it gets the people going

* chore: more

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <[email protected]>

* chore: change date

* chore: tighten up last section

* chore: change data

* chore: update per feedback

* chore(docs): replace absolute links with relative links (#12949)


<!--
  Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or
  ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->

## Description

Suggest a more complete structure to the example gatsby-config.js file

## Related Issues

Along with #12103 this PR fixes #11957

<!--
  Link to the issue that is fixed by this PR (if there is one)
  e.g. Fixes #1234, Addresses #1234, Related to #1234, etc.
-->

* chore(showcase): Add Assortment to site showcase (#13002)

## Description

Adding [assortment.io](https://assortment.io) to site showcase. Assortment is my Web Development blog that I've recently updated to Gatsby, Netlify, Netlify CMS and Emotion. It'd be cool to see it on the showcase 😃

* feat(gatsby-dev-cli): add verdaccio support (#11525)

* feat(gatsby-dev-cli): add verdaccio support [wip]

* yuck - don't look

* just to verify verdaccio

* fix gitignore and add htpasswd with dummy gatsby-dev user

* some logging to understand why it tries to handle all the packages

* just temporarily so it hopefully at least works

* moar data

* don't copy all the packages right now

* don't rely on package name starting with "gatsby" heuristic

* tmp commit

* tmp

* fs change

* tmp

* a

* updates

* remove random files that shouldn't be here

* tmp

* revert dep changes

* ignore changes to package.json created during publishing

* testing of dep change in gatsby-cli is picked up by gatsby-dev-cli

* let's see if gatsby-dev will handle case of no node_modules

* sanity check

* adjust console message

* add missing devDeps

* more missing devDeps

* grab package.json from unpkg if package is not yet installed locally

* correctly ignore package.json changes during publishing

* cleaning things up

* htpasswd loc

* restore gatsby package.json

* adjust ignore files

* gatsby-dev-cli: ignore tests

* remove extra ln

* less console output

* turns out you don't need htpasswd after all

* use exact when installing local packages  - timestamp is used in version

* why it failed?

* use yarn for publishing - see verdaccio/verdaccio#997

* v0.1.1

* add temporary .npmrc file to allow anonymous publishes

* add some jsdocs

* update yarn.lock

* oops

* debug why still can't publish anon

* adjust npmrc content

* doh

* Revert "debug why still can't publish anon"

This reverts commit fc1045a.

* handle package installation of deps didn't change

* skip version changes for packages in gatsby mono-repo, queue copying instead of doing it immediately

* fix tests

* packages stored in verdaccio storage seems to be picked up by jest and causing trouble, so let's ignore verdaccio storage directory

* bye "wat", you will be missed

* bail early to avoid conditional bracket hell

* more bailing early

* more concise

* new line

* use exaca to simplify running yarn

* clean up www/.gitignore

* handle not existing packages

* remove unused (was needed for basic auth)

* cleanup temp file changes when process exit in middle of publishing

* ops

* Apply suggestions from code review

Co-Authored-By: pieh <[email protected]>

* cleanup unpkg response handler

* move stuff around

* remove tmp comment

* document traversePackageDocs fn

* restrcuture files

* add basic tests for traversingPackageDeps

* add basic tests for generating packages to publish (based on dep graph)

* fix tests on windows

* handle circular dependencies when constructing list of packages to publish

* remove cat ;(

* restore original e2e-test script

* update gitignore

* chore(release): Publish

 - [email protected]
 - [email protected]
 - [email protected]
 - [email protected]
 - [email protected]
 - [email protected]

* chore(release): Publish

 - [email protected]

* docs(gatsby-dev-cli): Edit README (#13049)

* Build out Gatsby media information in docs (#12906)

* add video info, delete unnecessary stubs

Related to #12903

* fix internal link for html5 video section

* update videoTitle example

Co-Authored-By: marcysutton <[email protected]>

* Apply suggestions from code review

thanks for the feedback!

Co-Authored-By: marcysutton <[email protected]>

* incorporate feedback, make into real docs!!

* delete unused stubs

* Update docs/docs/working-with-video.md

Co-Authored-By: marcysutton <[email protected]>

* Update docs/docs/working-with-video.md

Co-Authored-By: marcysutton <[email protected]>

* chore(gatsby): fix domready package to be compatible with ie10 (#13027)

* changed domready package to domready-loaded which is compatible with ie10

* updated domready to @mikaelkristiansson/domready

* updated packages/gatsby to use @mikaelkristiansson/domready

* chore(release): Publish

 - [email protected]

* feat(gatsby-transformer-react-docgen): use local babel config for react-docgen (#12001)

* feat: use local babel config for react-docgen

BREAKING CHANGE: now uses the local babel config with a fallback

* Update README.md

* chore(release): Publish

 - [email protected]

* chore(docs): add “Why I used GatsbyJS (#12954)

Why I used GatsbyJS

<!--
  Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or
  ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->

## Description

<!-- Write a brief description of the changes introduced by this PR -->

## Related Issues

<!--
  Link to the issue that is fixed by this PR (if there is one)
  e.g. Fixes #1234, Addresses #1234, Related to #1234, etc.
-->

* feat(www): don't check for overview frontmatter (#13060)

Fixes `[[guidelist]]` not being replaced in few pages (i.e. in https://www.gatsbyjs.org/docs/winning-over-stakeholders/ )

The code is handling cases when there are no children (tried building locally and it worked just fine).

Follow up to this would be to clear `.md` files that use `overview` and adjust page query. But this is just quick fix.

* chore(docs): add starter library to docs sidebar under starters (#12963)

 40% of people visiting the starters page go here next, so we should probably add this:

![image](https://user-images.githubusercontent.com/4388699/55285012-58d26180-5337-11e9-9259-68e81b4894ad.png)

* chore(showcase): Add gmartinez.dev to showcase (#13067)

<!--
  Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or
  ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->

## Description

Adding gmartinez.dev to showcase list in site.yml

<!--
  Link to the issue that is fixed by this PR (if there is one)
  e.g. Fixes #1234, Addresses #1234, Related to #1234, etc.
-->


Co-authored-by: Lennart <[email protected]>

* fix(gatsby): don't try to statically analyze gatsby-node, require it and examine exports instead (#13053)

* fix: don't try to statically analyze gatsby-node, require it and examine exports instead

* differentiate test names

* Update packages/gatsby/src/bootstrap/resolve-module-exports.js

Co-Authored-By: pieh <[email protected]>

* chore(release): Publish

 - [email protected]

* Use Loki's elemMatch operator (#13025)

* feat(gatsby): add util.promisify polyfill for older node version (#13024)

* refactor(gatsby): gatsby develop: cleanup port detection (#13006)

* chore(release): Publish

 - [email protected]

* fix(gatsby): ignore __esModule export in gatsby-node exports (#13081)

I introduced bug/regression in #13053 by not removing `__esModule` export name from resolved export names - it break some plugins

Fixes: #13079

* chore(release): Publish

 - [email protected]

* fix(www): Hubspot form UI (#13080)

* fix(www): Work around HubSpot’s CSS being loaded

…by pulling in react-hubspot-form locally, and modifying it slightly. See comment in `www/src/components/react-hubspot-form` for more info.

* Fix `formInput` styles

… now matching the reference homepage newsletter form — no more Futura PT for input text.

* Return nothing because linter

* Make into Two Words

* Fix Comma Usage; Misc Updates (#13090)

Hopefully fix a code formatting issue when in a highlighted section.

* Fix Comma Usage; Misc Update (#13103)

* chore: format
@mikaelkristiansson mikaelkristiansson deleted the domready-for-ie10 branch May 4, 2019 21:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants