Default JS to Linux Hosting
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- azure, node.js, typescript
Research direction
No files, tests, or entry points are named. First confirm that the Linux offerings are generally available, then investigate where the default hosting behavior for JavaScript functions is defined. Done means the default changes from Windows to Linux, with the relevant behavior verified.
Written by the indexing model from the issue text.
Description
This shouldn't be considered until our Linux offerings are GA, but we should change the default hosting behavior for JS functions from Windows to Linux at some point in the future. Further exploration is needed but adding this as a tracking issue.
- Dominant language
- TypeScript
- Stars
- 110
- Forks
- 52
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from Azure/azure-functions-nodejs-worker
-
Handle valid prerelease Node.js versions without failing worker initializationPossibly taken @TsuyoshiUshio claimed this 43 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
area:nodejs-functions dependencies engineering tests
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Specialization race: double startApp() with stale require cache leaves worker on default v3 model with all functions unloadablePossibly taken @swapnil-nagar claimed this 49 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 30/100
Azure/azure-functions-nodejs-worker#838 · 1 comment ·
-
c-ares DNS misconfiguration on Windows Consumption causes mongodb+srv:// and dns.resolve*() failuresOpen
Difficulty 4/5 3-5 days Newbie friendliness 64/100
Azure/azure-functions-nodejs-worker#830 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
All issues in Azure/azure-functions-nodejs-worker
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
cockpit-project/cockpit-machines#2835 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cloudflare/kumo#866 ·
Maintainers usually reply within 1 day
-
area:connector bug
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tester-army/e2e#1015 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day