Skip to content

update client package entry point and types folder #58

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

Merged
merged 1 commit into from
Dec 19, 2019

Conversation

AllanZhengYP
Copy link
Contributor

This change will point Node package's entry point to the right place.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@kstich kstich merged commit ccb4ed4 into smithy-lang:master Dec 19, 2019
srchase pushed a commit that referenced this pull request Mar 23, 2023
* Ensure asynchronous region and credential resolution is covered by tests

* Factor SJCL-based SHA-256 into its own package to all usage without requiring all browser-based implementations

* Add an HTTP message serialization/parsing library

* Add support for switching to "S3 mode" via constructor parameters (applyChecksum = true and uriEscapePath = false)

* Add official sigv4 test suite

* Add a standalone NodeJS-based SigV4 package

* Add a standalone browser-based SigV4 package

* Add a standalone universal JS SigV4 package

* Specify base when parsing HTTP status codes

* Remove extra dependencies from crypto-sha256-browser

* Ensure tests in signature-v4 are all using crypto-sha256-js
srchase pushed a commit that referenced this pull request Jun 16, 2023
* Ensure asynchronous region and credential resolution is covered by tests

* Factor SJCL-based SHA-256 into its own package to all usage without requiring all browser-based implementations

* Add an HTTP message serialization/parsing library

* Add support for switching to "S3 mode" via constructor parameters (applyChecksum = true and uriEscapePath = false)

* Add official sigv4 test suite

* Add a standalone NodeJS-based SigV4 package

* Add a standalone browser-based SigV4 package

* Add a standalone universal JS SigV4 package

* Specify base when parsing HTTP status codes

* Remove extra dependencies from crypto-sha256-browser

* Ensure tests in signature-v4 are all using crypto-sha256-js
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

Successfully merging this pull request may close these issues.

2 participants