Skip to content

func new behaves differently for different core tools installs #4343

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jsumners-nr opened this issue Mar 28, 2025 · 0 comments
Open

func new behaves differently for different core tools installs #4343

jsumners-nr opened this issue Mar 28, 2025 · 0 comments

Comments

@jsumners-nr
Copy link

  1. mkdir some-project && cd some-project
  2. echo "{}" > package.json
  3. npm i -D azure-functions-core-tools
  4. export PATH=./node_modules/.bin:${PATH}
  5. func init --worker-runtime node --language javascript --model V4
  6. func new => list of 27 possible templates
  7. Choose the "HTTP Trigger" template and the generated code will not be at "model V4"

  1. mkdir some-project && cd some-project
  2. echo "{}" > package.json
  3. brew tap azure/functions && brew install azure-functions-core-tools@4
  4. func init --worker-runtime node --language javascript --model V4
  5. func new => list of 15 possible templates
  6. Choose the "HTTP Trigger" template and the generated code WILL be at "model V4"

I would expect that either method to result in the same code being generated. What is the difference? In either case, func --version reports "4.0.7030".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant