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

Convert gatsby-theme-ui-blog to TypeScript #711

Closed
wants to merge 2 commits into from

Conversation

epilande
Copy link
Contributor

Convert gatsby-theme-ui-blog to TypeScript.

Related to #668.

@epilande epilande requested a review from mxstbr February 24, 2020 02:58
@mxstbr mxstbr mentioned this pull request Mar 1, 2020
32 tasks
@hasparus hasparus self-assigned this May 10, 2020
Copy link
Member

@hasparus hasparus left a comment

Choose a reason for hiding this comment

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

I think it's okay after fixing conflicts and the two small issues I mentioned, but let's wait to see how we're going to approach TS in themes/plugins (#668 (comment))

"@theme-ui/preset-base": "^0.3.0",
"gatsby-plugin-react-helmet": "^3.1.3",
"gatsby-plugin-theme-ui": "^0.3.0",
"gatsby-theme-blog-core": "^1.0.2",
"gatsby-theme-ui-layout": "^0.3.0",
"react-helmet": "^5.2.1",
"theme-ui": "^0.3.1"
Copy link
Member

Choose a reason for hiding this comment

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

We should still have theme-ui in dependencies.

It's imported in

.

And then we don't need core and mdx.

Dependencies could look like this

  "dependencies": {
    "@emotion/core": "^10.0.0",
    "@mdx-js/react": "^1.0.0",
    "@theme-ui/preset-base": "^0.4.0-alpha.0",
    "gatsby-plugin-react-helmet": "^3.1.3",
    "gatsby-plugin-theme-ui": "^0.4.0-alpha.1",
    "gatsby-theme-blog-core": "^1.0.2",
    "gatsby-theme-ui-layout": "^0.4.0-alpha.0",
    "react-helmet": "^5.2.1",
    "theme-ui": "^0.4.0-alpha.1"
  },

Comment on lines +1 to +3
{
"extends": "../core/tsconfig"
}
Copy link
Member

Choose a reason for hiding this comment

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

This lands in user's node_modules. I think we can't reference core's tsconfig there.

Suggested change
{
"extends": "../core/tsconfig"
}
{
"compilerOptions": {
"resolveJsonModule": true,
"esModuleInterop": true,
"moduleResolution": "node",
"strict": true,
"jsx": "preserve"
}
}

@lachlanjc
Copy link
Member

Thank you so much for this contribution—unfortunately we’ve deprecated this package :(

@lachlanjc lachlanjc closed this Dec 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants