![]() They both have different versions of same libs (as well as other unrelated libs) Here's a new information I just saw: we have 2 lib/node_modules in the project. JVM: Java HotSpot(TM) 64-Bit Server VM by Oracle Corporation > As for your second screenshot (not resolving of "CoreService.getFromState" method), is "re" package declared in `./lib/package.json` under "dependencies" key?īuild #WS-162.1812.21, built on September 4, 2016 Thanks it will be easier to work already. Ok I don't remember it was the case before but I can live with scopes. Since "getFromState" is defined in a file from "lib/node_modules" library, it should be found in "Custom | Project and Libraries" scope. ![]() > Regarding your screenshot of "Find in Path" dialog, it's expected that "getFromState" is not found in the "Whole project" scope (which is the same as "Custom | Project files"). ![]() In which files you don't have code completion: your main application or `lib/node_modules/*` files? If it's your main application (that doesn't include `lib/node_modules` IIUC) then enabling "./lib/node_modules" should probably help. > Now we can't use the code completion or research stuff in our own code anymore. A small question regarding your original problem You've described lifecycle of lib/node_modules updates in detail. Will it bring expected code completion and navigation in your main application for modules imported from `lib/node_modules`? Please open "Settings | Languages & Frameworks | JavaScript | Libraries" and locate "/lib/node_modules" library. It means that the node_modules folder is simply excluded and direct dependencies (declared in lib/package.json under 'dependencies' key) are not indexed. Just noticed that your `lib/node_modules` folder is not marked as "library root" on your screenshot ( ). Thanks for the information and sorry for the late reply. It is not tracked into git (although we track a pack.7z). The root node_modules have no issues, it is used for build only and Webstorm behaves as expected (excluding it). We have a dozen apps developped by several teams, we rely on npm because when one of our lib is updated (and released on our private repo) we just have to mail the lead devs, make them npm update and push and voilà, all the teams have the latest version of the lib. We still use npm as I said above, when we need to update a lib the lead dev will npm update and commit on git. Our project files and lib/node_modules/* are indeed in the same git repository. The lead dev will npm update into /libs then commit on git.Įverything is registered into dependencies, no devDependencies: We have a package.json yes, because we need to update our own libs (in our private repository) as well as external libs. If you still need a sample project I can make one for you but it's difficult to justify the time to my hierarchy, we already had to argue in order for us to have licences for your products, they won't want to hear they slow us. With PayJunction's No-code Payments Integration, you can streamline your payment processing, reduce development time and costs, and generate additional revenue, all while providing your users with a seamless and efficient payment experience. Webstorm is now an obstacle for the dev: we have to manually search via scopes, or even remember the lib we want and open the file with shift+shift, look in the file and copy&paste the function name. Accelerate your development time and bring your payment solution to market faster. 7zip package into git we pack and unpack because of lack of trust in the npm system).īecause of the fact node_modules is automatically excluded, it is excluded from global search and sometimes from autocomplete. We didn't want that to pollute our git (we still have a. We separated the build related stuff and the front lib stuff because of the trillion files we can find in gulp and node modules. When we need to update our own libs (or an external one), the lead dev will npm update, check if everything is ok then commit and push for everyone to pull & use. We also had bad experiences of external lib with same version number but different dist. ![]() Because we want everything to work all the time, even without network (as long as you have the sources, the project works). The second one, lib/node_modules is registered into git. another into lib/node_modules with our own libraries as well as external front libraries (they all are linked into the index.html) one at the root of the project for build related stuff (gulp etc.)Ģ. We decided to have two separate node_modules:ġ. I wasn't available until now, late reply for me too.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |