Since its looking into src directory you should use. A package locator is an object describing one unique instance of a package in the dependency tree.
So, if you're not publishing your lib outside of the mono repo then this is solvable without moving everything to the root with newer tools and some configuration work. Since in package.json you have: 'moduleDirectories': 'nodemodules', 'src' Which says that each module you import will be looked into nodemodules first and if not found will be looked into src directory. Ive also deleted yarn.lock as well and the issue persists.
3) removing nodemodules and re yarn ing, to no avail. Another workaround that feels less hacky is to force the postinstall of the common workspace to run from the postinstall of the one that errors. 2) adding types/node in my package.json, which you all can see here. I've run into this same issue and can confirm the odd src/index.ts -> index.ts workaround does work. It does appear to be part of webpack 5 if you can use that. Some solutions I have already tried are: 1) adding a types: 'node' in my tsconfig.json, as you all can see below. Unfortunately if the lib ends up getting used by something built with webpack and you're using v4 you'll need to configure custom path resolution step because webpack doesn't support the "exports" field. The specific error mentioned would still exist with typescript's path resolution that can be resolved using the "baseUrl" and "paths" options in your tsconfig.json file at the root and then using "extends" to share that config. Try reinstalling by running the following: npm i eslint-plugin-prettierlatest -save-dev. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. A globally-installed ESLint cannot find a locally-installed plugin. I want this to effectively work as-if it's two seperate repos. I know this issue can be resolved by adding money to the paths array of money-standard-libs's tsconfig, but I want to depend on the built package as these will be published seperately. The "exports" field node 14 is an important change that should ultimately make supporting subdirectory exports easier but for now it only solves part of the problem since other tooling doesn't seem to respect the field yet. If ESLint is installed globally, then make sure eslint-plugin-prettier is also installed globally. TS2307: Cannot find module 'money' or its corresponding type declarations. "C:\Users\acer\AppData\Local\Temp\ng-GYuFL2\angular-errors.log" for further details.Moving to the root at builds works and avoids tooling issues but as mentioned it complicates building, especially for sharing in workspaces. I copy pasted all the required files(hopefully) and when I try to run the project using ng serve it throws this error An unhandled exception occurred: Cannot find module stack: I am trying to run my angular project on another system
0 kommentar(er)
