Skip to content
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

Calling a certain function from an external library results in Azure Function not being deployed for unknown reasons. #321

Open
jonganej opened this issue Dec 16, 2024 · 0 comments

Comments

@jonganej
Copy link

It took me a long time to find out this was the offensive code so I packaged a simple stripped down example of the code into this zip for reproducing: typescript-az-fn.zip

Steps I undertook:

  1. Create Typescript Function Project from VS Code with the Azure Function boilerplate code generator.
  2. Added reference to the library gltf-transform, specifically "@gltf-transform/core": "^4.1.0", "@gltf-transform/functions": "^4.1.0"
  3. Debug locally with func start - method appears. All good.
  4. Attempt to deploy to Azure Function with F1 -> Azure Functions: Deploy To Functions App. Deployment claimed to be successful, but no function found on Function page on Azure.
  5. Remove the offending line await doc.transform(textureCompress({targetFormat: 'jpeg', resize: [512, 512] })) which uses the gltf-transform/functions package and redeploy -> method shows up in Azure Function's page.

My question is hence, what is it in this library that does not play well with the NodeJS runtime of Azure Function?

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

No branches or pull requests

1 participant