gatsbyjs / gatsby-starter-wordpress-blog Goto Github PK

gatsby ci got error.
because the default branch of gatsbyjs/gatsby-starter-wordpress-blog is main.
Could you change default branch to master (temporary)?

[main 450cd6b] chore(create-gatsby): Use new image plugin (#29356)
 9 files changed, 17274 insertions(+), 1161 deletions(-)
 create mode 100644 src/templates/Page.js
 rename src/templates/{blog-post.js => Post.js} (100%)
 create mode 100644 yarn.lock
error: src refspec master does not match any.
error: failed to push some refs to 'https://****************************************@github.com/gatsbyjs/gatsby-starter-wordpress-blog.git'

Exited with code exit status 1

CircleCI received exit code 1

https://app.circleci.com/pipelines/github/gatsbyjs/gatsby/57590/workflows/b859ef00-b79a-4c8d-989c-c538f7f9e033/jobs/612613

  if [ -n "$(git status --porcelain)" ]; then
    git add .
    git commit -m "$COMMIT_MESSAGE"
    git push origin master
  fi

https://github.com/gatsbyjs/gatsby/blob/936c74ea7ff9965c993541bd8feea82e40c0919b/scripts/publish-starters.sh#L40

The README.md file mentions a gatsby-ssr.js file but it's nowhere to be found.

I was just following the instructions at

gatsby new some-blog https://github.com/gatsbyjs/gatsby-starter-wordpress-blog

But npm fails to install with

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"^17.0.1" from the root project
npm ERR!   peer react@"^16.9.0 || ^17.0.0" from [email protected]
npm ERR!   node_modules/gatsby
npm ERR!     gatsby@"^4.0.0" from the root project
npm ERR!     peer gatsby@"^4.0.0-next" from [email protected]
npm ERR!     node_modules/gatsby-plugin-image
npm ERR!       gatsby-plugin-image@"^2.0.0" from the root project
npm ERR!       1 more (gatsby-source-wordpress)
npm ERR!     11 more (gatsby-plugin-sharp, gatsby-source-filesystem, ...)
npm ERR!   8 more (react-dom, gatsby-plugin-image, gatsby-plugin-offline, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^0.13.0 || ^0.14.0 || ^15.0.0 || ^16.0.0" from [email protected]
npm ERR! node_modules/react-helmet/node_modules/react-side-effect
npm ERR!   react-side-effect@"^1.1.0" from [email protected]
npm ERR!   node_modules/react-helmet
npm ERR!     react-helmet@"^5.2.1" from the root project
npm ERR!     1 more (gatsby-plugin-react-helmet)
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 

Hi folks,

I am currently working on a headless setup with this starter. I'm not sure if I should be using the "home page starter" instead, but that looks more like it's for single-page applications. I've made good progress on my theme by working with the unit tests provided but noticed Gutenberg galleries use different classes than what is currently being used with the latest version of WordPress. I see the TODO on single and archive pages noting an issue with the postCSS that the wordpress package uses. Is this still an issue? I added @WordPress to my node modules and just took the new gallery code, cut and paste it over the old in the stylesheet that his been migrated locally, but I'm wondering if I should just be directly calling these stylesheets from the package itself instead of the copies that we have.

The copies are working great minus the gallery code needing updated, but I'm curious if I shouldn't get too ahead of myself if I'm doing things the "wrong" way.

As an aside, if I did decide to import the styles directly from the node_modules folder, should my overwrites for styles just go into my defauly styles.css? I assume yes, but Im worried this will lead to unused CSS, as It's been a while since I've done a GatsbyJS project and I can't recall if it strips out unused or overwritten css on build.

This repo is referenced in the 3.0 release, but is still using v2.

after running
gatsby develop

I get the following error:
Can't resolve 'mitt' in '...\project-folder.cache'
If you're trying to use a package make sure that 'mitt' is installed. If you're trying to use a local file make sure that the path is correct.

File: .cache\emitter.js:1:0

Hi everyone, I'm looking for a blog template via mobile phone.

Then, I found a bug.

For other information, my mobile screen is 6.53 inches.

I hope it can be solved.

Hey first off, I love this repo. I got a blog set up in no time. I've run into an issue where after about at 40-50 posts the deploy times become really long (in the 7-10 min range). Are there optimizations that can be done to reduce deploy times? Here is the portion of the Netlify log that takes the most time. Thanks again, really appreciate the work you've done!

After instantiating a fresh install, an NPM audit identifies the following errors:

1. engine.io (moderate severity): This vulnerability is related to uncaught exceptions in engine.io, which could lead to unexpected application behavior. More details are available here: GHSA-r7qp-cfhv-p84w

2. file-type (high severity): This vulnerability is associated with an infinite loop when processing a malformed MKV file. More details can be found here: GHSA-mhxj-85r3-2x55

3. immer (critical severity): This vulnerability is caused by prototype pollution in the immer package. Prototype pollution can allow attackers to modify an application's behavior, potentially leading to various security issues. More details are available here:

   • GHSA-c36v-fmgq-m8hx
   • GHSA-33f9-j839-rf8h
   • GHSA-9qmh-276g-x5pj

engine.io  4.0.0 - 6.2.0
Severity: moderate
Uncaught exception in engine.io - https://github.com/advisories/GHSA-r7qp-cfhv-p84w
fix available via `npm audit fix --force`
Will install [email protected], which is outside the stated dependency range
node_modules/engine.io
  socket.io  3.0.0-rc1 - 4.4.1
  Depends on vulnerable versions of engine.io
  node_modules/socket.io
    gatsby  2.32.8 - 4.25.4-alpha-initial-webhook-body.2 || 5.0.0-alpha-drupal-proxyurl.11 - 5.4.0-next.3
    Depends on vulnerable versions of socket.io
    node_modules/gatsby

file-type  13.0.0 - 16.5.3
Severity: high
file-type vulnerable to Infinite Loop via malformed MKV file - https://github.com/advisories/GHSA-mhxj-85r3-2x55
fix available via `npm audit fix --force`
Will install [email protected], which is a breaking change
node_modules/gatsby-source-wordpress/node_modules/file-type
  gatsby-source-wordpress  3.11.0-alpha-wordpress.44 - 3.11.0-next.0 || >=3.12.0-next.0
  Depends on vulnerable versions of @rematch/immer
  Depends on vulnerable versions of file-type
  node_modules/gatsby-source-wordpress

immer  <=9.0.5
Severity: critical
Prototype Pollution in immer - https://github.com/advisories/GHSA-c36v-fmgq-m8hx
Prototype Pollution in immer - https://github.com/advisories/GHSA-33f9-j839-rf8h
Prototype Pollution in immer - https://github.com/advisories/GHSA-9qmh-276g-x5pj
fix available via `npm audit fix`
node_modules/immer
  @rematch/immer  *
  Depends on vulnerable versions of immer
  node_modules/@rematch/immer

7 vulnerabilities (3 moderate, 3 high, 1 critical)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

What I did,

1. Installed 'gatsby new my-wordpress-gatsby-site https://github.com/gatsbyjs/gatsby-starter-wordpress-blog'
2. Open VS Code
3. Change gatsbyconfig.js to my local WP (Installed the required 2 plugins) tried not changing and the same result
4. Run gatsby develop

Result:
ERROR #98124 WEBPACK

Generating development SSR bundle failed

Can't resolve 'mitt' in 'D:\gatsby\my-wordpress-gatsby-site.cache'

https://prnt.sc/12mm1xx

What I tried:

• Remove package-lock.json
• Issue gatsby clean to purge
• Remove node_modules folder.
• Install the dependencies again
• Issue gatsby develop

Edit:
did npm install mitt and it seems to be working quite weird it is not installed on dependencies at a fresh install

First of all, thank you for building such a great starter. It has been an amazing journey.

I am having trouble with gatsby-inline-image not respecting the parent containers width or height.

Steps

• Clone repo
• Point gatsby-source-wordpress at my local Wordpress instance (local by flywheel)
• Unrelated? Added process.env.NODE_TLS_REJECT_UNAUTHORIZED=0 in gatsby-node.js)
• Add tailwind as per docs and some custom CSS
• Run gatsby-develop

Expected (on mobile)

Actual (on Mobile)

Image too wide, going beyond 100% viewport and causing a horizontal scroll bar.

Notes

• Updated all plugins to latest version
• Wordpress side is perfectly fine so it has to be something on the gatsby image transformation

See https://www.gatsbyjs.com/plugins/gatsby-image/