Skip to content

Commit 4ef3132

Browse files
authored
tweak netlify dev info
1 parent 8cd23db commit 4ef3132

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

Diff for: README.md

+3-5
Original file line numberDiff line numberDiff line change
@@ -22,14 +22,12 @@ If this sounds confusing, support is available through [our regular channels](ht
2222
<details>
2323
<summary><b>Netlify Dev vs. Netlify-Lambda</b></summary>
2424

25-
Some headline notes:
25+
[`Netlify Dev`](https://github.com/netlify/netlify-dev-plugin#what-is-netlify-dev) is incrementally adoptable. **`netlify-lambda` is still recommended if you need a build step for your functions**, as explained here:
2626

27-
- [`Netlify Dev`](https://github.com/netlify/netlify-dev-plugin#what-is-netlify-dev) is incrementally adoptable. **`netlify-lambda` is not deprecated and is still recommended for some situations**, as explained below.
28-
- Part of Netlify Dev serves unbundled function folders through [zip-it-and-ship-it](https://github.com/netlify/zip-it-and-ship-it) with no build step. This is likely to be attractive to many users who previously needed `netlify-lambda` for function folders.
29-
- However, if you want to use a build step for your functions (e.g. for webpack import/export, babel or typescript), you can use `netlify-lambda`, `tsc` or your own build tool to do this, just point Netlify Dev at your build output with the `functions` field in `netlify.toml`.
27+
- **When to use Netlify Dev**: Part of Netlify Dev serves unbundled function folders through [zip-it-and-ship-it](https://github.com/netlify/zip-it-and-ship-it) with no build step. This is likely to be attractive to many users who previously just needed `netlify-lambda` for bundling multi-file functions or functions with node_module dependencies.
28+
- **When to use Netlify Lambda**: However, if you need a build step for your functions (e.g. for webpack import/export syntax, running babel transforms or typescript), you can use `netlify-lambda`, `tsc` or your own build tool to do this, just point Netlify Dev at your build output with the `functions` field in `netlify.toml`.
3029
- Finally, We also want **existing `netlify-lambda` users to be able to use Netlify Dev with no change to their workflow**. This is done through the [Netlify Dev Function Builder](https://github.com/netlify/netlify-dev-plugin#function-builders-function-builder-detection-and-relationship-with-netlify-lambda) abstraction. It is, however, a very new feature with only simple detection logic for now, that we aim to improve over time. If it doesn't work well for you, you can simply not use Netlify Dev for now while we work out all your bug reports.
3130

32-
3331
</details>
3432

3533

0 commit comments

Comments
 (0)