lerna) and how you develop the code living in these monorepos.ĭid you add any special configurations to the IDE and/or package.json, tsconfig.
Please share your experience with yarn workspaces / monorepo (e.g. CLion and WebStorm and PhpStorm cost money, theres no dedicated Rust IDE. We have tried to tell IntelliJ to look into another folder for node_modules, but still not satisfying. A faster/lighter JetBrains IDE would beat everything in VSCode. The strange thing is that imports are not known but on the other hand most of the time you can navigate to the correct source / definition within the IDEs for the same import if you write it down manually. If you're already in VS Code for the Web at you can alternatively navigate to different repos via the Remote Repositories.
Since yarn workspaces will store most of the node_modules in the mono repo's root folder, the IDE (IntelliJ as well as VSCode) have problems resolving the imports to any node_modules when coding inside a "inner" project (so called "package" of a monorepo). Suggestions are populated by your browser search history, so if the repo you want doesn't come up, you can also type in the fully qualifiedMicrosoft has created an amazing product with VS Code which you can of course use for larger business applications. WebStorm has in its standard installation more features than VS Code has in its default installation without any additionally installed extensions. IntelliJ IDEA and WebStorm belong to 'Integrated Development Environment' category of the tech stack. WebStorm indexes entire your project, and after that, it knows your code better than you. VS Code is more of an editor than an IDE like WebStorm is categorized as. We use webpack to build and bundle and everything works well (especially the linking between local modules/packages). WebStorm is a lightweight and intelligent IDE for front-end development and server-side JavaScript. Working on a larger typescript project we decided to move the code to a monorepo with yarn workspaces.
0 kommentar(er)
