Upstream Pull 후 신규 Npm Build 시 이슈 발생...
nasa1515 opened this issue · comments
안녕하세요 줌코딩님 오랜만에 질문 남깁니다.!!
근 2달정도만에 줌코딩님이 새롭게 커밋하셨던 내용들 Upstream으로 Pull 받아서 Commit 하려 했으나
아래와 같은 이슈가 발생하는데 혹시 어느 부분에서 발생하는 건지 아실까요...?
기존에 있던 pages/index.js 파일과 Link 달아주신 pages/index.js 내용에 상이한 부분이 없는 것 같습니다.
혹시 짤려있는 Error가 있을까 싶어 전체 로그 전달 드립니다ㅠㅠ
- 추가적으로 Custom했던 gatsby-node.js 문제일까 싶어 현재 줌코딩님의 파일을 그대로 Overwrite 해도 동일한 이슈가 발생합니다.
(조금 더 알아보시기 쉽게 Blog Repo를 이슈가 발생한 대로 남겨두도록 하겠습니다.)
> nasa1515@1.1.0 start
> npm run develop
> nasa1515@1.1.0 develop
> gatsby develop
success open and validate gatsby-configs - 0.322s
warn Plugin gatsby-remark-images is not compatible with your gatsby version 2.32.13 - It requires gatsby@^3.0.0-next.0
warn Plugin gatsby-remark-prismjs is not compatible with your gatsby version 2.32.13 - It requires gatsby@^3.0.0-next.0
warn Plugin gatsby-remark-copy-linked-files is not compatible with your gatsby version 2.32.13 - It requires gatsby@^3.0.0-next.0
warn Plugin gatsby-remark-smartypants is not compatible with your gatsby version 2.32.13 - It requires gatsby@^3.0.0-next.0
success load plugins - 3.076s
success onPreInit - 0.124s
success initialize cache - 0.141s
success copy gatsby files - 0.490s
success onPreBootstrap - 1.913s
success createSchemaCustomization - 2.143s
success Checking for changed pages - 0.004s
success source and transform nodes - 1.121s
success building schema - 1.024s
ERROR
TeX parse error: Extra open brace or missing close brace
ERROR
(node:25472) Warning: a promise was rejected with a non-error: [object Array]
(Use `node --trace-warnings ...` to show where the warning was created)
ERROR #85901 GRAPHQL
There was an error in your GraphQL query:
Unexpected error value: ["TeX parse error: Extra open brace or missing close brace"]
File: gatsby-node.js:86:19
Error: Unexpected error value: ["TeX parse error: Extra open brace or missing close brace"]
- runMicrotasks
- task_queues:94 processTicksAndRejections
node:internal/process/task_queues:94:5
- async Promise.all
- async Promise.all
- async Promise.all
- async Promise.all
- async Promise.all
- graphql-runner.ts:187 GraphQLRunner.query
[my-blog]/[gatsby]/src/query/graphql-runner.ts:187:14
- gatsby-node.js:86 Object.exports.createPages
C:/Users/USER/Desktop/Blog/my-blog/gatsby-node.js:86:19
- api-runner-node.js:485 runAPI
[my-blog]/[gatsby]/src/utils/api-runner-node.js:485:16
ERROR
Error while running GraphQL query.
info Total nodes: 354, SitePage nodes: 1 (use --verbose for breakdown)
failed createPages - 5.919s
success Checking for changed pages - 0.002s
success createPagesStatefully - 0.301s
success update schema - 0.048s
success write out redirect data - 0.005s
success Build manifest and related icons - 0.220s
success onPostBootstrap - 0.235s
info bootstrap finished - 23.685s
success onPreExtractQueries - 0.003s
success extract queries from components - 1.319s
warn The GraphQL query in the non-page component "C:/Users/USER/Desktop/Blog/my-blog/src/templates/blog-template.js" will not be run.
Exported queries are only executed for Page components. It's possible you're
trying to create pages in your gatsby-node.js and that's failing for some
reason.
If the failing component(s) is a regular component and not intended to be a page
component, you generally want to use a <StaticQuery> (https://gatsbyjs.org/docs/static-query)
instead of exporting a page query.
If you're more experienced with GraphQL, you can also export GraphQL
fragments from components and compose the fragments in the Page component
query and pass data down into the child component — https://graphql.org/learn/queries/#fragments
success write out requires - 0.197s
warn You can't use childImageSharp together with author.gif — use publicURL instead. The childImageSharp portion of the query in this file will return null:
undefined
success run static queries - 0.578s - 3/3 5.19/s
ERROR
TeX parse error: Extra open brace or missing close brace
ERROR
(node:25472) Warning: a promise was rejected with a non-error: [object Array]
ERROR #85901 GRAPHQL
There was an error in your GraphQL query:
Unexpected error value: ["TeX parse error: Extra open brace or missing close brace"]
1 | query cUsersUserDesktopBlogmyBlogsrcpagesindexJs2043027757 {
2 | allMarkdownRemark(sort: {fields: frontmatter___date, order: DESC}) {
3 | edges {
4 | node {
5 | id
> 6 | excerpt(pruneLength: 500, truncate: true)
| ^
7 | frontmatter {
8 | categories
9 | title
10 | date(formatString: "MMMM DD, YYYY")
11 | }
12 | fields {
13 | slug
14 | }
15 | }
16 | }
File path: C:/Users/USER/Desktop/Blog/my-blog/src/pages/index.js
Url path: /
Plugin: none
Error: Unexpected error value: ["TeX parse error: Extra open brace or missing close brace"]
- runMicrotasks
- task_queues:94 processTicksAndRejections
node:internal/process/task_queues:94:5
- async Promise.all
- async Promise.all
- async Promise.all
- async Promise.all
- async Promise.all
- graphql-runner.ts:187 GraphQLRunner.query
[my-blog]/[gatsby]/src/query/graphql-runner.ts:187:14
- query-runner.ts:132 queryRunner
[my-blog]/[gatsby]/src/query/query-runner.ts:132:14
- queue.ts:70 Worker.process [as fn]
[my-blog]/[gatsby]/src/query/queue.ts:70:24
원석님 안녕하세요!
일단 저도 원석님 블로그 클론 받아 여러가지 시도를 해봤는데 원인을 파악하기가 쉽지 않네요😭
원석님 블로그 같은 경우에는 기본 테마에서 메타상으로 변경할 수 있는 것들 외에 코드를 변경하신 부분들이 있다보니,
제가 새로운 기능을 추가하고 업데이트 내용을 충돌없이 머지하기에는 어려움이 있어보입니다.
(이 부분까지 완벽하게 할 수 있는 방법은 저도 조금 더 찾아보도록 하겠습니다🙏)
제안드리는 방법으로는 pull 받기 이전의 상태로 블로그를 운영하시고,
버그 수정이 필요하신 부분들이 있다면 따로 말씀해주시면 추가적인 지원을 드리도록 하겠습니다.
원석님 다시한번 항상 블로그를 잘 사용해주시고 문제도 공유해주셔서 너무 감사합니다!
깔끔한 해결책을 못드려 죄송합니다!🙏
아닙니다!! 항상 이렇게 빠른 지원해주셔서 저야 말로 감사드립니다!!!