Dev Feed

2025-01-03

GitHub | vercel/next-learn

### What is the documentation issue? This [/redirects page](https://nextjs.org/docs/api-reference/next.config.js/redirects), which is referenced in the [status codes](https://nextjs.org/learn/seo/crawling-and-indexing/status-codes) section of the SEO learning module, is - ironically I must say - returning a 404 response. ### Is there any context that might help us understand? The redirects page is linked out to from the status codes SEO learning page. Presumably it should detail the setup of a 308 or show a 308 in action. ### Does the docs page already exist? Please link to it. https://nextjs.org/docs/api-reference/next.config.js/redirects

2025-01-03

GitHub | vercel/next-learn

### What is the documentation issue? [This /static-file-serving link](https://nextjs.org/docs/basic-features/static-file-serving) returns a 404. It is linked from the [robots-txt](https://nextjs.org/learn-pages-router/seo/crawling-and-indexing/robots-txt) page in the SEO learning module ### Is there any context that might help us understand? This is the 2nd link I've encountered in the SEO learning module that I've clicked out to that's returned a 404 (1st: https://github.com/vercel/next.js/issues/74410). Perhaps there's a broader issue at play? ### Does the docs page already exist? Please link to it. https://nextjs.org/docs/basic-features/static-file-serving

2024-12-30

GitHub | vercel/next.js

### What is the documentation issue? [This /static-file-serving link](https://nextjs.org/docs/basic-features/static-file-serving) returns a 404. It is linked from the [robots-txt](https://nextjs.org/learn-pages-router/seo/crawling-and-indexing/robots-txt) page in the SEO learning module ### Is there any context that might help us understand? This is the 2nd link I've encountered in the SEO learning module that I've clicked out to that's returned a 404. Perhaps there's a broader issue at play? ### Does the docs page already exist? Please link to it. https://nextjs.org/docs/basic-features/static-file-serving

2024-12-30

GitHub | vercel/next.js

### What is the documentation issue? This [/redirects page](https://nextjs.org/docs/api-reference/next.config.js/redirects), which is referenced in the [status codes](https://nextjs.org/learn/seo/crawling-and-indexing/status-codes) section of the SEO learning module, is - ironically I must say - returning a 404 response. ### Is there any context that might help us understand? The redirects page is linked out to from the status codes SEO learning page. Presumably it should detail the setup of a 308 or show a 308 in action. ### Does the docs page already exist? Please link to it. https://nextjs.org/docs/api-reference/next.config.js/redirects

2024-12-25

GitHub | bertrandom/chrome-cookies-secure

Not something i've managed to look into since my last post but it's on my radar when I get some time.

2024-12-01

StackOverflow | Badge

Active member for a year, earning at least 200 reputation

2024-11-27

GitHub | bertrandom/chrome-cookies-secure

I've got a linux machine up and running my side again now. Hopefully I'll be able to take a look over the next fortnight.

2024-11-18

GitHub | tj/node-blocked

I've added this dependency to a few lambda functions at global scope (outside of the `lambdaHandler` itself) and it's generating some illogical readings that don't line up with latencies being tracked for total lambda execution time (or overall latency measured from the client side including round-trip). Has anyone else come across extremely large readings for lambdas? Some of the lambdas are just doing validation and then fast dynamo db reads. No CPU intensive tasks. - 261 lambda invocations in an hour > 10s event loop block measurement - Arguments are 50ms threshold and 50ms interval - Node 20 Never seen anything like this in the 15-20 kubernetes services I've got this same dependency running in.

2024-11-09

GitHub | mledoze/countries

A blast from the past. Glad to see a decision made on it.

2024-11-01

StackOverflow | answer_posted

I didn't understand how this answer: https://stackoverflow.com/a/74317613/10732370 solved the issue. I've added a global hook and used the this binding to address the issue in our test suite. // hooks....