Regarding external private packages that are relied upon by firebase functions as well as "isolated" packages. #129
-
|
Hey, first off I want to say this is an awesome library and I greatly enjoy your write ups and seeing you pop up in various discussions across GitHub. Up until recently I was doing the relatively hacky solution of packing, installing and segmenting my functions from the rest of my mono repo ( I have a project structure that looks like the following: I have a package in the packages folder called "models" that also relies on an external library that's also installed in my firebase functions folder. When I try and deploy the project I get the following error: The
Am I just not using this isolate package correctly? Any help would be greatly appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Okay, I think i configured it more closely to how it should be done, but I'm still getting an error. This file does exist in that isolate/build output as well. |
Beta Was this translation helpful? Give feedback.
-
|
Solved! Okay, there were two changes that I made that I believe contributed to the solution here.
Thanks again for such an amazing package. This really ended up cleaning up my build process. |
Beta Was this translation helpful? Give feedback.
Solved!
Okay, there were two changes that I made that I believe contributed to the solution here.
/src/FirestoreTypesas apart of the index.ts file. I didn't catch that the LSP imported it that way because it was being packed with the build files, but not apart of the main entry-point for the package (the package.json'smainvsfilesfields). I actually suspect this was the primary issue when bundling everything together.Thanks again for such an amazing package. This really ended up cleaning up my build…