Home>
[What I did]
- In package.json, name is set to "app".
By doing so, app can be treated as the project root when importing each library,
import HomeScreen from 'app/src/screens/HomeScreen'
It was made possible to specify with etc.
When eslint is set, the above app cannot be read as the project root, and an import error occurs as eslint's judgment.
I thought it would work if I wrote eslintConfig in package.json, but eslint itself stopped working.
[]
I want to keep eslint aware of it while leaving the app.project root setting in package.json.
I have investigated various things, but I can't catch it. Can anyone give me advice?
-
Answer # 1
Related articles
- nodejs - please tell me how to use double quotes in double quotes in packagejson
- connection between nodejs and mysql
- nodejs - please tell me the difference in behavior between "declaring variables" and "array literal"
- asynchronous communication (post communication) between javascript and nodejs is not possible
- link between nodejs and json file does not work
- Nodejs how to set multiple startup commands in packagejson
- The version number of the library in packagejson in Nodejs (~ and ^)
- Example of creating packagejson with npm initialization in nodejs
- Nodejs method to update dependencies in packagejson to latest version
- Method for closing ESLint in NodeJs project
- Difference between nodejs resend and ressend
Self-solved.
By installing this library, I was able to set it with conditions.
https://www.npmjs.com/package/babel-plugin-root-import
At first, I wanted to use app/... as an alias to the root directory. . . The settings in ~/were successful with the settings described above for the library. Although it is supported by ~/instead of app /, it is a solution.