Jeremy

If you have this set to `true` it might be causing some issues. ``` widenClientFileUpload: false, ``` From the docs - ``` (property) widenClientFileUpload?: boolean Include Next.js-internal code and code...

Thanks @masenf - That makes sense. I probably need a better understanding of the request and state lifecycle. When I build a NextJS app _manually_, I can leverage SSR to...

Also, for reference, when using the _Pages_ routing mode, we could use the `getServerSideProps` function to provide the metadata. I'm still digging into the code, but I _think_ we could...

I've verified the `custom_code` can inject the `getServerSideProps` function in page, and NextJS doesn't complain. But I'm not sure this is the correct way to provide server side props, especially...

I also get the error - ``` TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".css" for ..... ``` But only when generating my types. It's definitely related to a custom lexical plugin,...

If I change my client feature to a default export instead of a named export, it works. So instead of - ``` { ClientFeature: { exportName: 'MyClientFeature', path: 'src/lexical/myfeature/index.client', },...

If the meter tags are different, could we `unregister` then `register` the meter with a combined list of tags? Also, am I looking at the right prometheus client implementation? https://github.com/prometheus/client_java/blob/master/simpleclient/src/main/java/io/prometheus/client/CollectorRegistry.java#L49