Azure / Azure/azure-functions-core-tools
Using Node runtime creates an obj directory which should have .funcignore on by deafault
- Dominant language
- C#
- Stars
- 1.5k
- Forks
- 498
- Avg merge
- 5d 4h
- Merged PRs (30d)
- 15
Description
Following on from the issue I created against the Node reference for Azure Functions:
[https://github.com/MicrosoftDocs/azure-docs/issues/21973](url)
When running locally using, the Nodejs runtime, an /obj folder is created. This should not be uploaded when publishing the project to the Azure platform and therefore .funcignore should be on by default to avoid confusion and issues.
Contributor guide
Research direction
The issue names no source file, test, or entry point. Start by tracing how the Node.js runtime creates the /obj directory and how Azure Functions Core Tools handles .funcignore during local publishing; done means the default behavior prevents /obj from being uploaded without requiring confusing manual setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100