piped.video/WFbvJ0dVlHk@allenholub I really liked your talk.
Here's a question if I may: when is the right time in the process to speak about technical tasks?
where do I fit/explain the work done to eg. setup a CI pipeline? incorporate better status codes? upgrade a library?
I'd like to make a reproduction but the codebase is large and can't come up with a simple one.
My setting is an nx monorepo with custom webpack to enable vanilla extract.
As soon as I import something into a .css.ts file I get this.
Welcome react-forget, welcome back React simplicity!!
It will take some time, but if this experimental compiler hits the ground, it's going to be the next-big-thing we were waiting for!
piped.video/lGEMwh32soc
Ah, right. I haven't found an example of that scenario and the official docs show this.
It doesn't show the "size" option but "useCallback" instead, any idea why?
I like being contradicted 🤣🤣.
Of course my "never do" was a pun, everyone is free to write code that makes sense to them, and I wouldn't reject a PR for that.
But it makes sense to reduce lines of logic-code in components, think of deps carefully and build reusable hooks.
A thunk is an anonymous function with no parameters of its own, that wraps one with arguments. This prevents the expression from being evaluated until a receiving function calls the anonymous function, thereby achieving lazy evaluation.
Ok env worked, but I have something else. A bit of context: server was working perfectly, then I wanted to put it in a docker compose, hence the need of env.
Stack trace points at github.com/Urigo/graphql-mes…
Could it be an issue with mesh or am I reading this wrongly?What is title?
Yes boy!YES!when in doubt rm node_modules and start again!the hooks error was just that, fixed...AND...your suggestion for trailingSlashes fixed my deployments once and for all!boom!
Thanks man!that would be axactly what I need, but super weird I can't recreate my own issue. It is working without those settings. The problem I have now though is that I can't statically export a project with react hooks. I'm getting this.
Although it's a nx project the app gets built on the hosting pkatform as a plain next app. If the two have different behaviours then my next.config.js will have to be different.
I tried uploading the build folder to now but it fails since it automatically tries to build it again is there a way to just upload and run next start?