Mike Kornelson
Mike Kornelson
I'll have to try to find the cause of this issue. I'm not a webpack master but I'll see what I can do.
Getting the webpack `resolve.root` configuration was the first place I went to, and works fine. The problem is that the server code doesn't resolve. I'm going to play with the...
Ok, I've done a bunch of testing on this branch. I cannot get webpack's `resolve.root` to work in production. It's possibly something to do with the dynamic `require` statements but...
Yeah. I like the explicitness of it too. I'm changing all of my code to use that. I use webstorm too! It does have aliasing built in via Resource Root...
Yup I agree. It's a start anyways. I'll have to dig further into why resolve.root is not working.
I'm seeing a strange issue with these types. I'm trying @AlkanV's v6.0 example. You define `DefaultNavigationProps` like this (in TYPE DEFINITIONS): `export type DefaultNavigationProps = NativeStackScreenProps;` In your SCREEN IMPLEMENTATION...