Tim Neutkens

Just to verify what @sw-yx said with regards to `git push`: > (i personally havent even tried it since we chatted.. old habits die hard) I'm trying out `gh` as...

Since it manages Github releases github enterprise support would be nice 👍 cc @leo

To clarify this: - `process.env.MY_API_KEY` -> not replaced by Next.js in any way - `process.env.NEXT_PUBLIC_ANALYTICS_ID` -> replaced by Next.js during `next build` - Reading `process.env.MY_API_KEY` in `getStaticProps` -> `MY_API_KEY` Needs...

Based on the code shared that route handler is static, doesn't use `request` values and no `export const dynamic = 'force-dynamic'`.

I don't think we should land this as it affects a different library than the first-party code that Next.js applies to. Sorry for the mixed signals here!

* **#61394** 👈 * `canary` This stack of pull requests is managed by Graphite. Learn more about stacking. Join @timneutkens and the rest of your teammates on Graphite

Hmm I guess we could disable the strict parsing for node_modules by default but I'm not opposed to having strict parsing by default in order to prevent unexpected behavior.

Seems the library is unmaintained so I'm going to remove the example in the Next.js repository instead. Thanks for the link @mischnic, super helpful! Will keep this issue open as...

@gurkerl83 I'm trying to understand what the problem is with the change that was landed, it implements exactly the behavior that is intended based on your hook: before it scrolls...

Just had a look at this and it seems to me that the behavior is correct, the reason it ends up overriding styles is that you're putting two different css...