nlap VS excelize-wasm

There is a problem with which IP ranges are used, as Microsoft-hosted build agents can be hosted in multiple regions. For example my DevOps organization is West Europe - Documentation (https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml) says following: "Your hosted agents run in the same Azure geography as your organization. Each geography contains one or more regions.". What means North and West Europe, but in the same document you can find following phrase - "Due to capacity restrictions, some organizations in the Brazil South or West Europe regions may occasionally see their hosted agents located outside their expected geography.". On top of that, every storage account can have up to 200 IP rules. Working on a tool for this kind of scenario(https://github.com/groovy-sky/nlap), which detects IP limit exceed and merges IP ranges to fit in 200. Another problem is that if source and destination Azure resources are in the same region - you need to allow access from VNet, as by using public IP that is not possible to be done. Writing a document about it - https://github.com/groovy-sky/azure/blob/master/paas-vnet-04/README.md#restriction-by-ip . As you don't have access to Microsoft build agents network environment you can't grant access for its VNets.

A pure WebAssembly / Javascript port of Go Excelize library named excelize-wasm NPM package has been production-ready use