Hi dev, the newsletter subscribe option is not working. Do I need to config it or it is pre configrd?

ProjectList opens Link in same page, ideal behavior should be to open link a new tab
tried passing ReactNode into its props but doesn't seems to work. Needs code to be updated.

There is an inconsistent behaviour in links to posts:
From the ProjectList the links have a trailing slash, e.g. /posts/my-post/
in links from BlogGallery there is none, e.g. /posts/my-post

On production I need a trailing slash in all links.
So in astro.config.mjs I had to set
trailingSlash: 'always'
and it worked.

And I had to append the trailing slash in the NavBar links, e.g.
<NavMenuItem href="/posts/">Blog Posts</NavMenuItem>

Hi,

It is crashing.

Heroku log:

2022-05-31T14:27:15.071913+00:00 app[web.1]: at ESMLoader.resolve (node:internal/modules/esm/loader:580:30)
2022-05-31T14:27:15.071913+00:00 app[web.1]: at ESMLoader.getModuleJob (node:internal/modules/esm/loader:294:18)
2022-05-31T14:27:15.071914+00:00 app[web.1]: at ModuleWrap. (node:internal/modules/esm/module_job:80:40)
2022-05-31T14:27:15.071914+00:00 app[web.1]: at link (node:internal/modules/esm/module_job:78:36) {
2022-05-31T14:27:15.071914+00:00 app[web.1]: code: 'ERR_MODULE_NOT_FOUND'
2022-05-31T14:27:15.071915+00:00 app[web.1]: }
2022-05-31T14:27:15.202525+00:00 heroku[web.1]: Process exited with status 1
2022-05-31T14:27:15.246512+00:00 heroku[web.1]: State changed from starting to crashed
2022-05-31T14:27:16.471684+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=png-blog.herokuapp.com request_id=ce919adb-5fdf-4ee1-a3ad-c688de24a158 fwd="3.141.28.136" dyno= connect= service= status=503 bytes= protocol=https
2022-05-31T14:27:16.750784+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=png-blog.herokuapp.com request_id=e6b9cc6e-3707-4e14-8147-55418567e3d0 fwd="3.141.28.136" dyno= connect= service= status=503 bytes= protocol=https
2022-05-31T14:29:07.775284+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=png-blog.herokuapp.com request_id=e9071cf0-87e9-4a56-9d23-60ea56aa3141 fwd="3.141.28.136" dyno= connect= service= status=503 bytes= protocol=https
2022-05-31T14:29:07.524376+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=png-blog.herokuapp.com request_id=9ec3b380-a478-4560-8782-6fb4c9d77ae3 fwd="3.141.28.136" dyno= connect= service= status=503 bytes= protocol=https
2022-05-31T14:33:49.384151+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/robots.txt" host=png-blog.herokuapp.com request_id=a25df73e-6367-40c6-b324-72a534e39271 fwd="94.130.167.87" dyno= connect= service= status=503 bytes= protocol=http
2022-05-31T14:33:50.597249+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=png-blog.herokuapp.com request_id=95a43440-0cfb-4211-8be6-4152f85fa8e8 fwd="94.130.167.87" dyno= connect= service= status=503 bytes= protocol=http

1. Adding extra Categories Tags breaks the UI fluidity on mobile apps.
2. Hero banner Avatar looks fine with provided image but its breaking other images that do not have transparent padding by default.

Also components do not take any style props or it could have been fixed by adding the right css style.

Hi, I created an astro plugin which allows to add Like buttons to blog posts.
Are you open to integrate it in your template? I can create a PR to setup the integration. It will be just a few line of code. I will make the integration optional, meaning that if the setting_key is missing (the user doesn't want to use the plugin), nothing is affected and will change.

In general, the plugin allows to receive any kind of feedback, but I think for a blogsite likes are more appropriate. Nonetheless, it's very easy and customizable.

Let me know.
Thanks.

I'm using the official Astro workflow for GitHub Action.
Build and deployment jobs are both completed with no errors.

When accessing the deployed page no images are displayed, and in the browser console a 404 error is logged for each of them.

Images not loading:

Errors in browser console:

Helo,

When i run npm run build, i got this error

D:\Landing\Astro-boilerplate>npm run build

> [email protected] build
> astro build

08:35:27 PM [build] Collecting build information...
08:35:37 PM [build] src/pages/index.astro is taking a bit longer to import. This is common for larger "Astro.glob(...)" or "import.meta.globEager(...)" calls, for instance. Hang tight!
08:35:41 PM [build] Completed in 14.50s.

 building client
vite v2.9.12 building for production...
✓ 23 modules transformed.
dist/entry.663e93a5.js   138.21 KiB / gzip: 44.18 KiB
Completed in 2.31s.

08:35:43 PM [build] Building entrypoints for prerendering...
08:35:47 PM [build] Completed in 3.81s.

 generating static routes
▶ src/pages/index.astro
  └─ /index.html (+92ms)
λ src/pages/rss.xml.ts
  └─ /rss.xml/index.html (+18ms)
▶ src/pages/posts/hello-world.md
  └─ /posts/hello-world/index.html (+19ms)
▶ src/pages/posts/second-post.md
  └─ /posts/second-post/index.html (+14ms)
▶ src/pages/posts/fifth-post.md
  └─ /posts/fifth-post/index.html (+16ms)
▶ src/pages/posts/first-post.md
  └─ /posts/first-post/index.html (+11ms)
▶ src/pages/posts/forth-post.md
  └─ /posts/forth-post/index.html (+11ms)
▶ src/pages/posts/sixth-post.md
 error   Input file is missing

please help.

Thanks

I ran the following commands:

git clone --depth=1 https://github.com/ixartz/Astro-boilerplate
cd Astro-boilerplate
npm install
npm run dev

I'm receiving this error:

> [email protected] dev /home/fernando/Documents/Empresa/Dev/Astro-boilerplate
> astro dev

(node:44380) UnhandledPromiseRejectionWarning: Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'react-dom' imported from /home/fernando/Documents/Empresa/Dev/Astro-boilerplate/node_modules/@astrojs/react/dist/index.js
    at new NodeError (internal/errors.js:322:7)
    at packageResolve (internal/modules/esm/resolve.js:732:9)
    at moduleResolve (internal/modules/esm/resolve.js:773:18)
    at Loader.defaultResolve [as _resolve] (internal/modules/esm/resolve.js:887:11)
    at Loader.resolve (internal/modules/esm/loader.js:89:40)
    at Loader.getModuleJob (internal/modules/esm/loader.js:242:28)
    at ModuleWrap.<anonymous> (internal/modules/esm/module_job.js:76:40)
    at link (internal/modules/esm/module_job.js:75:36)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:44380) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:44380) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Hello,
after npm install I have an error when I run npm run dev :

I want to add another page, projects. I added it in /src/pages, and inside added a directory pages, with a file [...page].astro. It seems if I create any page that isn't named posts (the one given by the template), I get an eslint error? Why is this?

arsing error: "parserOptions.programs" has been provided for @typescript-eslint/parser.
The file was not found in any of the provided program instance(s): src/pages/projects/[...page].astro

This is the error

When browsing https://creativedesignsguru.com/demo/astro-boilerplate/posts/ you can see on the network requests that the images are not being processed by astro-imagetools as the stock images get downloaded into the client.

The only image being transformed is located here: https://creativedesignsguru.com/demo/astro-boilerplate/posts/sixth-post/ so it seems to only be able to parse embedded images in a markdown file.

Any clues?

I get errors when I run 'npm run dev' because of these two dependencies. I tried using 'npm audit fix --force' but it doesn't fix the issue