Adrian Hall

Adrian Hall

Microsoft Program Manager by day; Mobile Developer by night

Reducing the deployment size of your JavaScript Azure Functions

January 12, 2020  1 minute read  

I’m doing some Azure Functions development in JavaScript at the moment, using the new azure-functions-core-tools. One of the features it has is command line publication, like this:

$ func azure functionapp publish my-function-app

I have a single function right now (called ping). Running the publish step creates a ZIP file:

$ npx func azure functionapp publish my-function-app               
Getting site publishing info...
Creating archive for current directory...
Uploading 187.62 MB [##---------------------------------------------------------------------]

That’s a big file. Wow! It creates a ZIP file of the whole directory!!!! My function isn’t that big!

Looking at the directories, it’s obvious which ones are the culprit:

$ du -ks */.           
462952  node_modules/.
8       ping/.
4       tools/.
$ du -ks node_modules/*/.
du -ks node_modules/*/. | sort -rn
451588  node_modules/azure-functions-core-tools/.
3600    node_modules/es5-ext/.
3088    node_modules/es-abstract/.
624     node_modules/ext/.
424     node_modules/type/.
412     node_modules/deferred/.
360     node_modules/resolve/.
156     node_modules/npm-run-all/.
128     node_modules/object-inspect/.
104     node_modules/es6-iterator/.
100     node_modules/es6-symbol/.
96      node_modules/object.assign/.
92      node_modules/timers-ext/.
88      node_modules/event-emitter/.
88      node_modules/es-to-primitive/.
80      node_modules/semver/.
# ...

Getting rid of azure-functions-core-tools from the published source would reduce the file size considerably. Fortunately, the tooling provides .funcignore for precisely this problem. Just add node_modules/azure-functions-core-tools to your .funcignore file. Now, the publication looks like this:

$ npx func azure functionapp publish my-function-app
Getting site publishing info...
Creating archive for current directory...
Uploading 1.7 MB [##########################################################################]
Upload completed successfully.

It knocked about 4 minutes from my publication time, and reduced the file size down to under 2MB.

If you use TypeScript, you should also add the node_modules/typescript package to the .funcignore as that is pretty big too.

Of course, this doesn’t mean anything if the functions don’t work at the end of it. I’m happy to report that my ping API works just fine, so the azure-functions-core-tools isn’t required within the publish package. It’s also given me 5-10 minutes back per publication cycle.

Leave a comment

You may also enjoy

Create an App Registration for RBAC with PowerShell and Microsoft Graph.

January 19, 2024  5 minute read  

I’m currently working on some automation within Azure to deploy a hub-spoke web application. This web application authenticates with Entra ID using an App Registration and Role-Based Access Controls (RBAS) using App Roles. So, I need to create an app registration, enterprise app, and create the app roles.

Azure Mobile Apps: Supporting tables with int Id

December 22, 2023  14 minute read  

One of the persistent questions I get asked about Azure Mobile Apps is how to support older tables. Let’s say you have an older application that was never designed for mobile applications. It likely has a model like this:

Deleting Azure resources the right way.

July 12, 2023  3 minute read  

If you are an Azure developer, you likely spin up an application, do some work, then shut it down again. However, shutting down resources and deleting them has an order to them. If your service is network isolated (in a virtual network), then you can’t delete the application until the private endpoints are shut down. Budgets don’t get deleted with the resource group. Diagnostic settings can’t be deleted if the resource no longer exists. There is an order you should do things:

Purge Azure API Management soft-deleted services with ease.

January 20, 2023  4 minute read  

I work a lot with Azure API Management, which means I turn up and down services quite a few times a day. Azure API Management has an awesome feature that prevents you from accidentally deleting a service, called soft-delete. Instead of immediately deleting the service, it marks it as soft deleted and purges it later on. Unfortunately, that means that you can’t immediately reuse that service name. In production, this is a great thing to have. In development, it turns into a pain. That’s b...