/route to be a path to a file in the repo/branch that's hosting. This breaks stuff hardcore for us, and aws makes it easy to handle that without issue.sub -> dom; dom branch now reflects what is actively hosted.
1
1
4
2
2
discord-replica component so my markdown page isn't a messy pile of codeflexbox, which is great for linear content that you want positioned quickly. We should be able to nest a grid inside, as long as a div is defined to isolate it and set a new block-parent to target.
Hope that makes sense. I don't have a ton of time to actively dev on this, but I will be helping with code reviews and deployments.flexbox, which is great for linear content that you want positioned quickly. We should be able to nest a grid inside, as long as a div is defined to isolate it and set a new block-parent to target.
Hope that makes sense. I don't have a ton of time to actively dev on this, but I will be helping with code reviews and deployments. <span class="channel">discord-name</span> we instead had a channel component and i could just do <Channel>discord-name</Channel>
nav_link and img-box classes supposed to be for?nav_link and img-box classes supposed to be for? nav_link used to do the styling for navigation links. XD
If I recall correctly, the purpose was to bring a general consensus to links on the page that were for page to page navigation, as opposed to links to external sites.nav_link used to do the styling for navigation links. XD
If I recall correctly, the purpose was to bring a general consensus to links on the page that were for page to page navigation, as opposed to links to external sites. img_box puts the image in a container element. That way, I can position the container, which is generally a lot more reliable than trying to position a img elementimg_box puts the image in a container element. That way, I can position the container, which is generally a lot more reliable than trying to position a img element waffle@iron:~/workspace/tacosblaseball.com$ npm run build
> [email protected] build
> next build
info - Using webpack 5. Reason: Enabled by default https://nextjs.org/docs/messages/webpack5
info - Checking validity of types
Failed to compile.
./components/DiscordList.js
10:13 Error: Missing "key" prop for element in iterator react/jsx-key
./components/Footer.js
8:9 Warning: passHref is missing. See https://nextjs.org/docs/messages/link-passhref @next/next/link-passhref
./components/Header.js
9:11 Warning: passHref is missing. See https://nextjs.org/docs/messages/link-passhref @next/next/link-passhref
Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-ruleswaffle@iron:~/workspace/tacosblaseball.com$ npm run build
> [email protected] build
> next build
info - Using webpack 5. Reason: Enabled by default https://nextjs.org/docs/messages/webpack5
info - Checking validity of types
Failed to compile.
./components/DiscordList.js
10:13 Error: Missing "key" prop for element in iterator react/jsx-key
./components/Footer.js
8:9 Warning: passHref is missing. See https://nextjs.org/docs/messages/link-passhref @next/next/link-passhref
./components/Header.js
9:11 Warning: passHref is missing. See https://nextjs.org/docs/messages/link-passhref @next/next/link-passhref
Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules waffles@iron:~/workspace/tacosblaseball.com$ npm run build
> [email protected] build
> next build
info - Using webpack 5. Reason: Enabled by default https://nextjs.org/docs/messages/webpack5
info - Checking validity of types
info - Creating an optimized production build
Failed to compile.
ModuleNotFoundError: Module not found: Error: Can't resolve './pages/vault' in '/home/gsmith/workspace/tacosblaseball.com'
> Build error occurred
Error: > Build failed because of webpack errors
at /home/gsmith/workspace/tacosblaseball.com/node_modules/next/dist/build/index.js:15:924
at async Span.traceAsyncFn (/home/gsmith/workspace/tacosblaseball.com/node_modules/next/dist/telemetry/trace/trace.js:6:584)
Looks like a cyclic dependancy error$1, which requires $2
1Error: Image Optimization using Next.js' default loader is not compatible with `next export`.
Possible solutions:
- Use `next start` to run a server, which includes the Image Optimization API.
- Use any provider which supports Image Optimization (like Vercel).
- Configure a third-party loader in `next.config.js`.
- Use the `loader` prop for `next/image`.
Read more: https://nextjs.org/docs/messages/export-image-api<Image> component and removed the Spinny component. Just pushed, it should be showing up shortly.
(edited)npx next build and/or npx next export locally without error.