You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-Added `deleteAll` option to delete all functions in a project.
24
-
-Added new executable `read-env` to read the environment variables.
35
+
- Made esbuild work on linux
36
+
- Added `deleteAll` option to delete all functions in a project.
37
+
- Added new executable `read-env` to read the environment variables.
25
38
26
39
## 2.1.0
27
40
28
41
### Changes
29
42
30
-
-Added `pnpmFix` option to fix pnpm install issues with firebase-tools and firebase-functions. It will npm install each functions and use the global firebase-tools to deploy.
31
-
-Fix firestore and document function deploy
43
+
- Added `pnpmFix` option to fix pnpm install issues with firebase-tools and firebase-functions. It will npm install each functions and use the global firebase-tools to deploy.
44
+
- Fix firestore and document function deploy
32
45
33
46
## 2.0.0
34
47
35
48
### Changes
36
49
37
-
-Migrated all functions to v2.
38
-
-Now all firestore triggers needs to be under `firestore` folder, `database` folder is not used for real time database triggers.
39
-
-Removed v1 support for firebase functions, now only v2 is supported.
50
+
- Migrated all functions to v2.
51
+
- Now all firestore triggers needs to be under `firestore` folder, `database` folder is not used for real time database triggers.
52
+
- Removed v1 support for firebase functions, now only v2 is supported.
40
53
41
54
## 1.1.0
42
55
43
56
### Changes
44
57
45
-
-Added support for AWS SAM deploy and logs
46
-
-Removed esbuild-plugin-alias, now esbuild looks directly at tsconfig.json for paths
47
-
-Made import paths relative to fix for windows users
48
-
-Added CFD_FUNCTION_NAME env to each function, so you can use it in your code, example setting tags to sentry.
58
+
- Added support for AWS SAM deploy and logs
59
+
- Removed esbuild-plugin-alias, now esbuild looks directly at tsconfig.json for paths
60
+
- Made import paths relative to fix for windows users
61
+
- Added CFD_FUNCTION_NAME env to each function, so you can use it in your code, example setting tags to sentry.
49
62
50
63
## 1.0.0
51
64
52
65
### Changes
53
66
54
-
-Added support for multiple firebase projects, not just prod and dev
55
-
-Updated function cache, the parameters are now a object instead of a string
56
-
-It now passes in the flavor
57
-
-Removed firebaseProjectProdId, firebaseProjectDevId, prodEnvFileName and devEnvFileName
58
-
-Made flavors required
59
-
-Renamed dev to development and prod to production
60
-
-Renamed functions-config.{flavor}.ts to script.config.{flavor}.ts
61
-
-Now scripts can use prompts from the user
62
-
-Support node18
67
+
- Added support for multiple firebase projects, not just prod and dev
68
+
- Updated function cache, the parameters are now a object instead of a string
69
+
- It now passes in the flavor
70
+
- Removed firebaseProjectProdId, firebaseProjectDevId, prodEnvFileName and devEnvFileName
71
+
- Made flavors required
72
+
- Renamed dev to development and prod to production
73
+
- Renamed functions-config.{flavor}.ts to script.config.{flavor}.ts
-Support for multiple [environments](https://firebase.google.com/docs/functions/config-env)
39
-
-Esbuild for faster builds
40
-
-Detect changes and only deploy changed functions
41
-
-No longer export all functions in a index.ts file, but deploy each function individually for smaller bundles
42
-
-Configurable deploy options
43
-
-Deploy with Node 14/16/18/20 and esm
44
-
-Cloud functions v2 support
45
-
-Deploy rules and indexes
46
-
-Execute scripts locally
47
-
-Read env file and copy to clipboard
48
-
-Cloud cache support
49
-
-Run emulators locally
50
-
-AWS SAM: build, deploy and watch logs for lambda functions
37
+
- Auto alias support
38
+
- Support for multiple [environments](https://firebase.google.com/docs/functions/config-env)
39
+
- Esbuild for faster builds
40
+
- Detect changes and only deploy changed functions
41
+
- No longer export all functions in a index.ts file, but deploy each function individually for smaller bundles
42
+
- Configurable deploy options
43
+
- Deploy with Node 14/16/18/20/22 and esm
44
+
- Cloud functions v2 support
45
+
- Deploy rules and indexes
46
+
- Execute scripts locally
47
+
- Read env file and copy to clipboard
48
+
- Cloud cache support
49
+
- Run emulators locally
50
+
- AWS SAM: build, deploy and watch logs for lambda functions
51
51
52
52
## Install
53
53
@@ -63,7 +63,7 @@ It uses esbuild to bundle your functions and then uses the [firebase-tools](http
63
63
64
64
## Prerequisites
65
65
66
-
-You will need to have the [firebase-tools](https://www.npmjs.com/package/firebase-tools) installed. Either globally or locally in your project. If you install it globally you have to set `packageManager` option to `global`.
66
+
- You will need to have the [firebase-tools](https://www.npmjs.com/package/firebase-tools) installed. Either globally or locally in your project. If you install it globally you have to set `packageManager` option to `global`.
67
67
68
68
```bash
69
69
pnpm i -D firebase-tools
@@ -257,13 +257,13 @@ It is recommend to have the following folder structure, but it is not required.
257
257
258
258
The folders in controllers will different deployment types:
The default function names will be the path from the `api/callable/database/scheduler` folder to the file. For example, the function `controllers/api/stripe/webhook_endpoint.ts` will be deployed as `stripe_webhook_endpoint`.
0 commit comments