Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Lucas Clay
    @mlclay
    @emillime Not all modules/packages are available in v3 yet.
    I think these are the currently available 'clients': https://github.com/aws/aws-sdk-js-v3/tree/master/packages
    Emil Raksanyi
    @emillime
    @mlclay Can I connect to AppSync using something else in v3? Or do I just wait..
    Lucas Clay
    @mlclay
    Sorry, I'm not actually familiar with using AppSync. I've been keeping up with the clients in v3 myself for some of my own projects though.
    Alex Jurkiewicz
    @alexjurkiewicz
    is there an online api reference for v3?
    Timothy Johnson
    @RedHatter
    There doesn't seem to be any service for the Cognito User Pools API? As far as I can tell there's only client-cognito-identity-browser which is for federated identity pools. Is this correct that the servers hasn't be implemented yet, or am I missing something?
    Chase Coalwell
    @srchase
    @alexjurkiewicz Each of the clients that have been published so far have documentation on their READMEs
    for any of the clients that have not yet been published, you can build them yourself
    Chase Coalwell
    @srchase
    after npm install/npm run bootstrap/npm test, you can run node ./packages/package-generator/build/cli.js client --model models/cognito-identity/2014-06-30/service-2.json --runtime node
    @emillime, you can try out the AppSync client by building it the same way.
    Frederic Rudman
    @frudman
    is there a general roadmap for v3? (url?) or a ballpark at least: 3 months? 6 months? > 1 year?
    Chase Coalwell
    @srchase
    @frudman Are you looking for timeline on General Availability?
    Frederic Rudman
    @frudman
    @srchase eventually yes (of course). But now just to see if it's worth experimenting with as well as starting the migration (understanding that there will be breaking changes).
    @srchase The app we're working on will not be production ready for another 6 months or so. So if V3 lands around then (or before or a little later), that's worth the coding investment now (for us). If longer, we'd wait before changing the code base.
    dgoenka
    @dgoenka
    When using AWS Lambda from the modularised stack I'm getting : "request.js:149 GET https://169.254.169.254/latest/meta-data/iam/security-credentials/ net::ERR_ADDRESS_UNREACHABLE" (First message - not sure what more details should I add when posting here).. worked fine when I was using the all in one version
    Moyo George
    @ThatOneAwkwardGuy
    is there a v3 package for EC2? not sure if im missing it or not
    Max Harris
    @maxharris9
    hey, does anyone have guidance on this? aws/aws-sdk-js#2015
    whoops, this is an AWS SDK v2 question
    Max Harris
    @maxharris9
    I really do need help though, because it's clear that v3 isn't an option given that it won't be out until winter!
    Amit Prakash Ambasta
    @ambasta
    Does the V3 SDK have support for step functions?
    Amit Prakash Ambasta
    @ambasta
    Additionally, npm run test is broken on the repo
    Mark Smith
    @markmsmith
    I have a similar question to frudman did a few months back - I'm starting a new Node project that's using Typescript and I'm interested in using the v3 API from the get-go, but the decision will depend on when GA is planned for the library. Is there any updated information available about that? I couldn't see any milestones declared in github with the set of issues that were still outstanding.
    Mark Smith
    @markmsmith
    @srchase bump^ ?
    Chase Coalwell
    @srchase
    @markmsmith we're not able to provide any commitments on expected GA for v3. We'd love to have you try out the new version and would welcome any feedback.
    V2 and V3 can run side-by-side in the same project, which will be useful for partial migrations.
    Mark Smith
    @markmsmith
    ok, thanks anyway.
    Brian Takita
    @btakita
    Hello, I'm excited about this project. Is the cognito-idp api currently supported?
    Thomas Gick
    @thgick
    NPM package not found for @aws-sdk/client-lambda-browser
    Any ideas?
    Chase Coalwell
    @srchase
    @thgick only a handful of clients have been published to NPM.
    until all the clients are published, you'll need to install from source.
    @btakita yes, node and browser clients were committed to the repository recently, but not yet published to NPM.
    Thomas Gick
    @thgick

    @srchase thanks for clarification.

    I cloned the repo locally to C:\localdev\aws-sdk-js-v3
    If i do the following:

    C:\localdev\aws-sdk-js-v3> npm link
    C:\localdev\myproject> npm link aws-sdk-js-v3
    C:\localdev\myproject> npm install @aws-sdk/client-cognito-identity-browser

    not the local package gets installed.
    Can you tell me what to do in order to install the local version in the namespace @aws-sdk?

    Lucas Clay
    @mlclay
    Since aws-sdk-js-v3 is a monorepo, do you need to cd clients/browser/client-cognito-identity-browser before you npm link? (entirely a guess)
    Thomas Gick
    @thgick

    @mlclay Thanks for your tip! i tried it out with one of the 2 packages i need. In this case client-lambda-browser.

    client-lambda-browser $ npm link
    npm WARN deprecated istanbul@0.4.5: This module is no longer maintained, try this instead:
    npm WARN deprecated npm i nyc
    npm WARN deprecated Visit https://istanbul.js.org/integrations for other alternatives.
    npm WARN deprecated @types/handlebars@4.1.0: This is a stub types definition. handlebars provides its own type definitions, so you do not need this installed.
    npm ERR! code E404
    npm ERR! 404 Not Found - GET https://registry.npmjs.org/@aws-sdk%2fclient-documentation-generator - Not found
    npm ERR! 404
    npm ERR! 404 '@aws-sdk/client-documentation-generator@^0.1.0-preview.2' is not in the npm registry.
    npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
    npm ERR! 404 It was specified as a dependency of 'client-lambda-browser'

    Do i really need to link the dependencies beetween the packages by hand?

    Lucas Clay
    @mlclay
    @thgick Unfortunately I believe you do. I did a little looking and came across the npm-link-shared module and it was created because of the issue described here. Sounds similar to your issue so it might help? https://60devs.com/simple-way-to-manage-local-node-module-using-npm-link.html
    Thomas Gick
    @thgick

    @mlclay i tried it with npm-link-shared with different options but got the same error "ignored due to missing or erroneous package.json" all the time:

    npm-link-shared /localdev/aws-sdk-js-v3 /localdev/myproject @aws-sdk/client-cognito-identity-browser --include-peer —include-dev
    Will be installing modules from /localdev/aws-sdk-js-v3/ to /localdev/myproject/...
    Restricted to the following modules [ '@aws-sdk/client-cognito-identity-browser' ]
    /localdev/aws-sdk-js-v3/clients ignored due to missing or erroneous package.json
    /localdev/aws-sdk-js-v3/models ignored due to missing or erroneous package.json
    /localdev/aws-sdk-js-v3/node_modules ignored due to missing or erroneous package.json
    /localdev/aws-sdk-js-v3/packages ignored due to missing or erroneous package.json
    /localdev/aws-sdk-js-v3/scripts ignored due to missing or erroneous package.json

    Lucas Clay
    @mlclay
    Did you have any luck? Didn't have any time to look at this over the long weekend, but looking at the error now it might be worth trying to give npm-link-share the path to the clients/browser directory
    npm-link-shared /localdev/aws-sdk-js-v3/clients/browser /localdev/myproject client-cognito-identity-browser --include-peer --include-dev
    Again, just guessing. I've still not tried using v3 at all myself. I'm waiting a little longer for a more finalized version
    Thomas Gick
    @thgick

    Hi Lucas,

    thanks for asking. Unfortunately not.

    I tried the command you wrote which looked promising:

    Will be installing modules from /localdev/aws-sdk-js-v3/clients/browser/ to /localdev/myproject/...
    Restricted to the following modules [ 'client-cognito-identity-browser' ]

    But as i installed the "client-cognito-identity-browser" with the following command, it turned out that the version from npm (preview.2) and not the local version (preview.5) was installed.

    npm i @aws-sdk/client-cognito-identity-browser -s

    Do i actually need to use the scope "@aws-sdk" while installing the locally linked module?
    I don't get how to differentiate between the remote npm version and the local version ^^

    Any help very appreciated :)

    Lucas Clay
    @mlclay
    @thgick I looked back at your original post and it looks like you're only trying to link because the modules weren't published and so you cloned. You hadn't been working on changes to the v3 package, correct? Reason I ask is because there's a separate scope for the v3 preview @aws-js-sdk-v3-prerelease. The specific package you need has a few versions published under that scope on npmjs so you may be able to skip the npm-link stuff completely
    Try this: npm i -S @aws-js-sdk-v3-prerelease/client-cognito-identity-browser@0.1.0-preview.5
    There's a couple different preview versions in that package to pick from. https://www.npmjs.com/package/@aws-js-sdk-v3-prerelease/client-cognito-identity-browser
    I didn't know about that separate scope before now. Hopefully that works for you. The npm linking may have been an unnecessary step :)
    Thomas Gick
    @thgick

    Hi Lucas, thank you very much. You're right, i only want to use the most current version of "client-cognito-identity-browser" and "client-lambda-browser".
    With your provided command i was able to install the current version of "client-cognito-identity-browser" but not of "client-lambda-browser".
    This was the error i got: 404 Not Found: @aws-js-sdk-v3-prerelease/client-lambda-browser@0.1.0-preview.1

    In the meanwhile I'm ready to give up ;) I can't understand that there is not a straight forward way to build the sdk from source which is described somewhere ^^

    AllanFly120
    @AllanFly120
    Hey @thgick I'm working on the instruction for installing clients from source, I hope this would be helpful😊 aws/aws-sdk-js-v3#352
    Thomas Gick
    @thgick
    @AllanFly120 Thank you very much! I will check it out. 👍
    AllanFly120
    @AllanFly120
    Btw, all the service clients have been released to NPM: aws/aws-sdk-js-v3#357
    Lucas Clay
    @mlclay
    This is great! Thanks Allan