snorreks / nx-cloud-functions-deployer Goto Github PK

the deployed function bucket didn't change and stayed with the default bucket
only the region is changed

@snorreks
thanks for the updates ^^

sadly now I have this issue but the deployment working as usual I think it's cloud caching again.

getOptionsFromCode SyntaxError: Expected property name or '}' in JSON at position 3
at JSON.parse ()
at wt (/home/mostafa/Documents/Firebase-NX/node_modules/.pnpm/[email protected][email protected]/node_modules/nx-cloud-functions-deployer/executors/deploy/index.js:12:5728)
at Ue (/home/mostafa/Documents/Firebase-NX/node_modules/.pnpm/[email protected][email protected]/node_modules/nx-cloud-functions-deployer/executors/deploy/index.js:12:4845)
at async Promise.all (index 2)
at async qe (/home/mostafa/Documents/Firebase-NX/node_modules/.pnpm/[email protected][email protected]/node_modules/nx-cloud-functions-deployer/executors/deploy/index.js:12:7682)
at async Promise.all (index 0)
at async Mt (/home/mostafa/Documents/Firebase-NX/node_modules/.pnpm/[email protected][email protected]/node_modules/nx-cloud-functions-deployer/executors/deploy/index.js:30:3766)
at async promiseToIterator (/home/mostafa/Documents/Firebase-NX/node_modules/.pnpm/nx@17.2.7_@swc-node+register@1.6.8_@swc[email protected]/node_modules/nx/src/command-line/run/run.js:30:11)
at async getLastValueFromAsyncIterableIterator (/home/mostafa/Documents/Firebase-NX/node_modules/.pnpm/nx@17.2.7_@swc-node+register@1.6.8_@swc[email protected]/node_modules/nx/src/utils/async-iterator.js:13:19)
at async iteratorToProcessStatusCode (/home/mostafa/Documents/Firebase-NX/node_modules/.pnpm/nx@17.2.7_@swc-node+register@1.6.8_@swc[email protected]/node_modules/nx/src/command-line/run/run.js:41:29)

this error appears to me when trying to deploy functions

at ChildProcess._handle.onexit (node:internal/child_process:286:19)
at onErrorNT (node:internal/child_process:484:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -2,
code: 'ENOENT',
syscall: 'spawn node',
path: 'node',
spawnargs: [
'--no-warnings',
'--import',
'tsx',
'********'
]
}
I got this error when trying to deploy.

is the structure changed for the rules?
NX ENOENT: no such file or directory, scandir '/home/mostafa/Documents/Firebase-NX/apps/rules/src/controllers'

auth().onCreate()
beforeUserCreate()
beforeUserSignin()

I have enabled the option pnpm to use the global firestore_tools but is still failing.,
any suggestions?

when I try to deploy with options for any function rather than callable functions are not working

@snorreks

Hi, how are the development process supposed to work with this sctructure? Looking at the code I see that you have an emulate target but it is not documentet, the same with build. Am I supposed to keep a separate firebase.json to emulate all the functions at once? And build using deploy --dry? (the build target seem to have some issues with paths when called directly)

Adding it as an option would be great for easier debugging.

Hi, the documentation states that database and firestore will behave the same structurally. However, it seems there are some issues with using this with realtime db, first of all there are no helpers for rtdb triggers so only way is to use the onValueCreated/Deleted/Updated, but then you'll have to provide the ref yourself and the path from the structure isn't used if I understand correctly.

Also, if you have the same collections in both firestore and database the triggers will get the same names and files are overwritten. Maybe prefix (or suffix) these triggers optionally with fs_ and db_/rt_ ?

Since rtdb triggers also have the option to have more advanced patterns inside the [] identifier (e.g ref: "/user/{uid=*@gmail.com}") and also that triggers react to both /user/123 and /user/123/notification/123/message this structure might not be suitable (or at least limitations should be documented)