gatsby-starter-default VS cli

upper@DESKTOP-6JTLCIP:/mnt/c/Users/Usuario/Codes/wsite/oportunidades-ilimitadas$ gatsby new board https://github.com/gatsbyjs/gatsby-starter-default info Creating new site from git: https://github.com/gatsbyjs/gatsby-starter-default.git

{ "name": "gatsby-starter-default", "private": true, "description": "A simple starter to get up and developing quickly with Gatsby", "version": "0.1.0", "author": "Kyle Mathews ", "dependencies": { "babel-plugin-styled-components": "^2.0.7", "gatsby": "^5.7.0", "gatsby-image": "^3.11.0", "gatsby-plugin-google-fonts-with-attributes": "^1.0.8", "gatsby-plugin-google-gtag": "^5.7.0", "gatsby-plugin-image": "^3.7.0", "gatsby-plugin-manifest": "^5.7.0", "gatsby-plugin-robots-txt": "^1.8.0", "gatsby-plugin-sharp": "^5.7.0", "gatsby-plugin-sitemap": "^6.7.0", "gatsby-plugin-styled-components": "^6.7.0", "gatsby-source-filesystem": "^5.5.0", "gatsby-source-wordpress": "^7.7.0", "gatsby-transformer-sharp": "^5.5.0", "react": "^18.2.0", "react-dom": "^18.2.0", "styled-components": "^5.3.6", "universal-cookie": "^4.0.4" }, "devDependencies": { "prettier": "^2.8.3" }, "keywords": [ "gatsby" ], "license": "0BSD", "scripts": { "build": "gatsby build", "develop": "gatsby develop", "format": "prettier --write \"**/*.{js,jsx,ts,tsx,json,md,css}\"", "start": "gatsby develop", "serve": "gatsby serve", "clean": "gatsby clean", "test": "echo \"Write tests! -> https://gatsby.dev/unit-testing\" && exit 1", "deploy": "gatsby clean && gatsy build && gatsby prepend && node deploy" }, "repository": { "type": "git", "url": "https://github.com/gatsbyjs/gatsby-starter-default" }, "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" } }

module.exports = { siteMetadata: { title: `Gatsby Default Starter`, description: `Kick off your next, great Gatsby project with this default starter. This barebones starter ships with the main Gatsby configuration files you might need.`, author: `@gatsbyjs`, siteUrl: `https://gatsbystarterdefaultsource.gatsbyjs.io/`, }, plugins: [ `gatsby-plugin-image`, 'gatsby-plugin-postcss', { resolve: `gatsby-source-filesystem`, options: { name: `images`, path: `${__dirname}/src/images`, }, }, `gatsby-transformer-sharp`, `gatsby-plugin-sharp`, { resolve: `gatsby-plugin-manifest`, options: { name: `gatsby-starter-default`, short_name: `starter`, start_url: `/`, background_color: `#663399`, // This will impact how browsers show your PWA/website // https://css-tricks.com/meta-theme-color-and-trickery/ // theme_color: `#663399`, display: `minimal-ui`, icon: `src/images/gatsby-icon.png`, // This path is relative to the root of the site. }, }, ], }

To make it even easier for you, we went ahead and created a Clerk + Gatsby starter repository. It has Clerk integrated with Gatsby's default starter.

First of all, we might have to be familiar with Gatsby as this article will skip over a lot of stuff to get to the point. Gatsby does provide a starter project. Importantly, we can definitely extend the website to have multiple pages such as blog, about, contact, etc.

Check your gatsby-config to see if the static query folder is setup. For example, if it’s an images, you need to setup the path. Check out this

gatsby new happy-paws https://github.com/gatsbyjs/gatsby-starter-default

Because sometimes I make idiotic mistakes and I really don't want that embarrassing stuff out there where people can see. I ran head first into an npm bug once when I tried to symlink the README file which resulted in the thing getting published without a README.

https://github.com/npm/cli/issues/6746

Embarrassing. And then they slapped me with a stupid 24 hour count down on top of it. I seriously hate this thing.

This is the same NPM that made a change causing the `integrity` field to go silently missing from `package-lock.json` [0] when installing packages, and then also not complaining at any other time in the future.

[0] https://github.com/npm/cli/issues/4460

Node.js v21 includes npm v10.2.0, which notably introduces a new sbom command that allows you to generate a Software Bill of Materials (SBOM) for the current project. You can read more about the changes in recent NPM releases on GitHub.

npm ERR! This is an error with npm itself. Please report this error at: npm ERR! https://github.com/npm/cli/issues

You'll need an AWS account and AWS credentials configured locally. We'll use pnpm but you could also use npm or yarn. The finished app is available on github.

~/Documents/amplify-hackathon/amplify-react-graphql-demo main !5 ?3  npm install -g @aws-amplify/cli  1 ✘ 4s 22:11:35 changed 26 packages in 25s 7 packages are looking for funding run `npm fund` for details npm notice npm notice New minor version of npm available! 9.4.0 -> 9.6.5 npm notice Changelog: https://github.com/npm/cli/releases/tag/v9.6.5 npm notice Run npm install -g [email protected] to update! npm notice

10 18.95 npm notice Changelog: https://github.com/npm/cli/releases/tag/v9.6.4

npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated npm WARN deprecated [email protected]: This SVGO version is no longer supported. Upgrade to v2.x.x. added 1692 packages, and audited 1699 packages in 23s 211 packages are looking for funding run `npm fund` for details 27 vulnerabilities (1 low, 7 moderate, 18 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 Run `npm audit` for details. npm notice npm notice New minor version of npm available! 9.5.1 -> 9.6.2 npm notice Changelog: https://github.com/npm/cli/releases/tag/v9.6.2 npm notice Run npm install -g [email protected] to update! npm notice