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

DO NOT MERGE!!! This PR is meant to test what in package-lock.json breaks netlify #55

Closed
wants to merge 1 commit into from

Conversation

sielay
Copy link
Collaborator

@sielay sielay commented Mar 24, 2018

No description provided.

@sielay
Copy link
Collaborator Author

sielay commented Mar 25, 2018

By luck found that. It refers to same problems. That has to do something with webpack config, so ned to dig into gatsby again. https://stackoverflow.com/questions/49193838/webpack-ts-loader-throws-error-that-property-makehot-is-missing-on-type-nodemo

@@ -7,7 +7,7 @@
"scripts": {
"start": "gatsby develop",
"develop": "gatsby develop",
"build": "gatsby build",
"build": "npm run patch && gatsby build",
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@@ -40,11 +41,11 @@
"gatsby-plugin-google-analytics": "latest",
"gatsby-plugin-manifest": "latest",
"gatsby-plugin-offline": "latest",
"gatsby-plugin-sharp": "latest",
"gatsby-plugin-sharp": "^1.6.31",
Copy link
Collaborator Author

Choose a reason for hiding this comment

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


return (
return (
<Provider store={store}>
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

#54

render() {
const { pathname } = this.props.location;
const isHome = pathname === "/";
export default (props: DefaultLayoutProps): JSX.Element => {
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Some changes around typings make that TS is picky about class form components here.

@fabien0102
Copy link
Owner

@sielay I close this PR, normally it's resolve 😄

@fabien0102 fabien0102 closed this Mar 27, 2018
@sielay
Copy link
Collaborator Author

sielay commented Mar 27, 2018

Is it? Ok. Let's do it. I think we still have a problem when upgrading packages. Will take a look.

@fabien0102
Copy link
Owner

If you have any needs, you can of course reopen this PR 😉 It's just to cleanup a little bit my "todo list" ^^

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