You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a couple of 11ty sites derived from this project (THANK YOU!) and am recently unable to build any of them, locally or in production. They all return the ETIMEDOUT error noted below. So, this morning I made a raw/unmodified clone of this project and tried running it locally. The output is as you see below, same ETIMEDOUT error as my other instances.
I haven't a clue why this is or what to do about it. The 54.243.162.8 reference appears to be an Amazon component?
$ npm start
> smol-11ty-starter@1.0.0 start
> eleventy --serve
(node:92199) [DEP0128] DeprecationWarning: Invalid 'main' field in '/Users/mark/GitHub/smol-11ty-starter/node_modules/emitter-mixin/package.json' of 'y'. Please either fix that or report it to the module author
(Use `node --trace-deprecation ...` to show where the warning was created)
> connect ETIMEDOUT 54.243.162.8:443
`Error` was thrown:
Error: connect ETIMEDOUT 54.243.162.8:443
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1571:16)
The text was updated successfully, but these errors were encountered:
The example link in the comment at the bottom of the src/_data/catpic.js file would be a good replacement, as would using placekitten. Viewing the demo on a desktop, my view of the image looks to be 1024px square, so a placekitten alternative would be https://placekitten.com/1024/1024.
I have a couple of 11ty sites derived from this project (THANK YOU!) and am recently unable to build any of them, locally or in production. They all return the ETIMEDOUT error noted below. So, this morning I made a raw/unmodified clone of this project and tried running it locally. The output is as you see below, same ETIMEDOUT error as my other instances.
I haven't a clue why this is or what to do about it. The 54.243.162.8 reference appears to be an Amazon component?
The text was updated successfully, but these errors were encountered: