Dev server serves stale JSON when functions use `import` statement for JSON
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 474
- Avg merge
- 23h 30m
- Merged PRs (30d)
- 53
Description
Describe the bug
When a Netlify function imports a JSON file with import myJson from './my.json', it will only ever return the contents of ./my.json as they were when the dev server was started, even after ./my.json is modified while the server is running.
While import statements only run once when executing the file, Netlify functions are AWS Lambdas which are expected to be executed from scratch and thus run the import statement with every execution. But netlify dev doesn't behave this way, only reloading the function's code when the actual code is changed.
This is an issue in development: I'm working on translating an application, and the translations go into a JSON file. A netlify function returns the corresponding language's JSON which is loaded with an import statement. The result is that as I add new strings to the JSON file, the function only ever returns the JSON file as it was when the dev server was started. The only way is to kill and restart the dev server.
Steps to reproduce
- Create a JSON file with these contents:
{}at./my.json - Create a Netlify function with these contents:
// netlify/functions/jsonTest.js
import myJson from './my.json'
const handler = event => {
return {
headers: { "Content-Type": "application/json" },
statusCode: 200,
body: JSON.stringify(myJson)
}
}
export { handler }
- Start the dev server with
netlify dev curl localhost:8888/jsonTest- Get
{}as the response - Without stopping the dev server, overwrite
./my.jsonwith these contents:{"netlify":"rocks"} curl localhost:8888/jsonTest- Get
{}as the response, instead of the current contents for./my.json - Kill the dev server
- Start the dev server again with
netlify dev curl localhost:8888/jsonTest- Get
{"netlify":"rocks"}as the response
Note that every once in a while, it will actually reload the function and re-run the import statement so you'll get the updated contents for the JSON file. But most of the time, it doesn't and serves stale contents
Configuration
[dev]
autoLaunch = false
[build]
command = "astro build"
functins = "netlify/functions"
publish = "dist"
[functions]
node_bundler = "esbuild"
Environment
System:
OS: Linux 5.15 Linux Mint 20.3 (Una)
CPU: (8) x64 Intel(R) Xeon(R) E-2134 CPU @ 3.50GHz
Memory: 12.83 GB / 46.93 GB
Container: Yes
Shell: 5.0.17 - /bin/bash
Binaries:
Node: 18.15.0 - ~/.nvm/versions/node/v18.15.0/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v18.15.0/bin/yarn
npm: 9.8.1 - ~/.nvm/versions/node/v18.15.0/bin/npm
pnpm: 8.9.2 - ~/.nvm/versions/node/v18.15.0/bin/pnpm
npmPackages:
netlify-cli: ^16.8.0 => 16.8.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the behavior with netlify dev, netlify/functions/jsonTest.js, the imported my.json file, and the [functions] node_bundler = "esbuild" configuration. Compare the curl response before and after changing my.json without restarting the server; done means the function returns the updated JSON while the dev server remains running.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- cli, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100