You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I mean, in react/react-native I do have a package.json inside every namespace:
-src
--assets
----package.json
--components
----package.json
--containers
----package.json
...
And every single package.json has the below (depends of the folder name) definition:
{
"name": "assets",
"version": "1.0.0"
}
So, if I need to get an specific asset, instead to use require('./../assets/logo.png');
I use require('assets/logo.png');
No matter where (deep) I'm getting this element, I just need to use this friendly syntax.
Is that possible?
The text was updated successfully, but these errors were encountered:
Hello @gersonmontenegro ,
so sorry for the late response.
I think you can try to achive what you need editing the open-file-from-path.regExp option in the plugin's configuration.
Thank you!
I mean, in react/react-native I do have a package.json inside every namespace:
-src
--assets
----package.json
--components
----package.json
--containers
----package.json
...
And every single package.json has the below (depends of the folder name) definition:
So, if I need to get an specific asset, instead to use
require('./../assets/logo.png');
I use
require('assets/logo.png');
No matter where (deep) I'm getting this element, I just need to use this friendly syntax.
Is that possible?
The text was updated successfully, but these errors were encountered: