glenveegee

@orbweaver I had the same error when calling CopyObject. I've managed to get the call working for CopyObject. I suspect the changes might fix the CreateMultiPartUpload call too. If you're...

@springcomp I'm updating it as we speak. Just been busy.

Steps to replicate: ```sh npx create-react-app test cd test npm run eject ``` that results in the following package.json ```json { "jest": "^24.5.0", "jest-pnp-resolver": "^1.2.1", "jest-resolve": "^24.5.0", ... } ```...

To be clear, after installing the latest jest-pnp-resolver the JSON looks as follows: ```json { "jest": "23.6.0", "jest-pnp-resolver": "^1.2.1", "jest-resolve": "23.6.0", ... } ```

Hi all, I hope no-one minds but I've rewritten the entire jmespath.js repo in typescript. https://github.com/nanoporetech/jmespath-ts If you find it a worthy replacement for the current `jmespath.js` package you're welcome...

We've implemented this in a slightly different way while still maintaining validation and interpreter scoping within the function. It also helps to add any number as a series of plugins...

We've written a typescript version of the project if you're interested in checking that out https://github.com/nanoporetech/jmespath-ts

Hey @Thaina. Just pushed the Typescript version to NPM. Check it out and let me know how it goes. https://www.npmjs.com/package/@metrichor/jmespath The README is updated and includes the `registerFunction` example.

We've implemented this in a slightly different way while still maintaining validation and interpreter scoping within the function. It also helps to add any number as a series of plugins...

Hi all, I hope it's not too presumptuous but we've rewritten the entire jmespath.js repo in typescript. It's 100% spec compliant with a few fixes and a bit of tidying...