Dillon
Dillon
According to this comment, v2 uses ES6 modules https://github.com/microsoft/ApplicationInsights-JS/issues/301#issuecomment-442542939
I thought that might be the case. If that's so, then I think the docs should describe this and provide an alternative installation guide. My current workaround installation is something...
It turns out it's not sufficient. After this mangled installation, husky is not executing lint-staged on pre-commit 🙁
Revised workaround installation: 1. `npx mrm lint-staged` - This will fail, that's expected 2. Fix the npm prepare script - `"prepare": "husky install"` -> `"prepare": "cd pathToYourRepoRoot && husky install...
I think this happens because ACE and JET sample the column to determine a type before the data gets to LinqToExcel. Usually I would expect it to take to type...
I see the same for Azure-hosted agents. Version 4 works fine but 5 fails saying it could not find a deployment.
The wildcard worked! Thanks @melborp The documentation on the filter states: > Optional string to filter deployments by. This can be useful if you have concurrent deployments to the same...