ijxy

Ok, but _why_? It doesn't make sense as it is now. You can't make the case that it is about security, because then it would also apply to non-NEXT_PUBLIC variables...

> This is based on my reading of the relevant instructions in the middleware documentation, which has explicitly stated that the next.config.js has the highest priority. > 1. headers from...

@pedroalmeida415 "use client" does not mean "client only", it means "send all the JS to the client". In a nutshell, you are trying to use the library as one would...

> @jxdp That looks good to me, do you want to submit a PR? Sure thing: https://github.com/mui/material-ui/pull/42786

@anagstef @tmilewski Apologies for the delay–I have updated as per comments and extracted the changed words into a little dictionary object so it is easier to see what is actually...

Can you provide an example of a project structure that this would actually be useful for? I am having a difficult time thinking of any that isn't extremely convoluted by...

@SainteCroquette Still not really understanding. This is the exact problem that a monorepo solves--using packages. In other words, why would you use inherited tsconfig paths instead of dependencies? ```json //...

> Could you expand a bit on sharing tsconfig files via dependencies and how this would allows you to merge to path configurations together (or is this another way to...

@saltman424 > Now you could take your point more generically, that mono-repos are outside the scope of TypeScript. I.e. the burden of making TypeScript useful in mono-repos is entirely on...

@dkamins I don't think that a magic "..." string is a very compelling option. Given that you have very specific requirements, I suggest that you _generate_ your TSConfig files using...