by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Chase Coalwell
    @srchase
    @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
    AllanFly120
    @AllanFly120
    Hey folks, I created a discussion issue here: 👉aws/aws-sdk-js-v3#372 Your inputs are very welcome!
    JoLo
    @jolo-dev
    Hi everyone,
    Does anyone of you have some experience by using Vue and loading the shared credentials files?
    Mark Stosberg
    @markstos
    I maintain the node-ses package, which is a very focused Node module that just does mail sending with AWS SES. The module is aging now and could stand to be updated with a promise-based API. A fork has added promise support, but lacks some of the latest features we've added. I'm definitely in favor of the direction the SDK is taking to allow installing and just a single module. The one big place for improvement is with the documentation. You can do better. If you check out the node-ses docs, it's a really good user experience. You can quickly find an example and the documentation for the key methods.
    The docs for the AWS official alternative are OK, but I'd rather see more complete docs for the SES APIs shipped right in the NPM module: https://www.npmjs.com/package/@aws-sdk/client-ses-node Surely there's a way to automate slicing and dicing the API docs to make that happen.
    Trivikram Kamat
    @trivikr
    Hi everyone, this is Trivikram - maintainer of AWS JavaScript SDK
    We're looking forward to hear from you about v2-style (idiomatic) vs command style (modular) in aws/aws-sdk-js-v3#364
    Please provide your valuable feedback, if you have a specific preference over one or the other
    Miguel Espinoza
    @purefan
    I got late to the convo but imo its more important to have one clear "default"/"encouraged"/"best practice". When people write tutorials and articles you don't want to wonder why are they importing "the same thing" in more than one way
    Mike Love
    @mike-love_gitlab
    I am using the new preview v3 aws-sdk
    (import { DynamoDBClient, ScanInput, ScanCommand, ScanOutput } from ‘@aws-sdk/client-dynamodb-v2-node’;)
    I have a method in a repository class (source below) that makes a simple scan of a DDB table.
    The aim with the method getDevicesList() is to use the async / await pattern on the ddbClient.scan()
    I have stripped the method to only structure and logging at each step.
    My question, why is the log statement ‘After DevicesScan...’ not appearing in the log?
    My assumption is that the method is completing before the ddbClient.send promise completes, which is consistent with what in the log.
    My expectation is that the execution will block until promise resolution. What am I missing?
    async getDevicesList(): Promise<DeviceEntity[]> {
    const devices: DeviceEntity[] = [];
    const command = new ScanCommand({
    TableName: ‘Device’,
    });
    try {
    this.logger.log(‘Get From DDB’);
    const devicesScanResult = await this.ddbClient.send(command);
    this.logger.log(‘After DevicesScan : ’ + JSON.stringify(devicesScanResult));
    for (const item of devicesScanResult.Items) {
    this.logger.log(‘Processing Item : ’ + JSON.stringify(item));
    }
    } catch (error) {
    this.logger.log( ‘Error Getting DeviceEntities List From DynamoDB’ + JSON.stringify(error) );
    }
    return devices;
    }
    Jedediah Smith
    @jedsmith13
    The question I have that brought me here is that I am having issues with using the CloudFrontClient to do a CreateInvalidationCommand. It is trying to use cloudfront.us-east-1.amazonaws.com for the hostname but is getting an ENOTFOUND error for getaddrinfo. What should I be setting the region to or is there some setting I am missing something?
    const elasticBeanstalk = new CloudFrontClient({
      region: 'us-east-1',
    });
    
    export const createInvalidation = async () => {
      const params = {
        DistributionId: DISTRIBUTION_ID,
        InvalidationBatch: {
          CallerReference: String(new Date().getTime()),
          Paths: {
            Quantity: 1,
            Items: ['/index.html'],
          },
        },
      };
    
      const createInvalidationCommand = new CreateInvalidationCommand(params);
      await elasticBeanstalk.send(createInvalidationCommand);
    };
    Parth Mehta
    @pash90
    Hi everyone! New here :)
    I have a question regarding the @aws-sdk/credential-provider-cognito-identity
    I raised an issue on the aws/aws-sdk-js-v3#564 but its been a while and no one responded so I thought I could get some help here
    The issue is around some variable being undefined in the compiled version of the @aws-sdk/credential-provider-cognito-identity
    Anyone have any ideas how I can go about fixing it?
    Tom Medema
    @tommedema
    Hi I'm starting a new project to upload multipart chunks from browser the s3. Should I use aws sdk for javascript version 2 or 3?
    And where is the documentation for V3?
    Tom McLaughlin
    @tmclaughbos_twitter
    Who questions here. first, what packages should I be using? I see packages with -node on the end and packages without. I think the ones without are the latest and greatest. That correct?
    Second. Can't figure out why this request returns an HTTP 400 with a Validation esception. https://gist.github.com/tmclaugh/0d4f4838d909e0e0e623194b7e3f50e6
    Tom McLaughlin
    @tmclaughbos_twitter
    Also, how do I set the log level?
    Tom McLaughlin
    @tmclaughbos_twitter
    installing @alpha fixes it
    Kristian Lundström
    @Mousaka
    client.send(
              new GetObjectCommand({
                Bucket: "pdf-template-dev",
                Key: `cool-key/${path}`
              })
            )
    How can I store the response in a buffer from a GetObjectCommand this? Can anyone link example code ? Thank

    I can only find this in the docs but I don't quite get it

    For operations containing stream response like GetObject(), you can get response stream by accessing to streaming member. e.g. data.Body.pipe(/ some writable stream /).(data is the resolved response object)

    Kristian Lundström
    @Mousaka
    (using @aws-sdk/client-s3-node)
    Kristian Lundström
    @Mousaka
         client.send(
              new GetObjectCommand({
                Bucket: bucketName,
                Key: `cool-key/${path}`
              }).then(response =>
               const receiveObject = new Promise<Buffer>(resolve => {
               const forBuffer = new PassThrough();
               response.Body?.pipe(forBuffer);
               const buffers: any[] = [];
               forBuffer.on("data", chunk => {
                 return buffers.push(chunk);
               });
               forBuffer.on("finish", () => {
                return resolve(Buffer.concat(buffers));
            });
          }));
    Got this to work eventually but it's a bit messy
    Logan Powell
    @loganpowell
    :wave: New guy here
    Logan Powell
    @loganpowell
    Is there a planned release date for v3 to come out of beta?
    Amit Prakash Ambasta
    @ambasta
    Where do I find documentation on various clients?
    Gigin George
    @gigincg
    Is the v3 sdk compatible with TypeScript?
    1 reply
    Gary Stidston-Broadbent
    @garysb
    hi all, has anyone tried running this on Deno?
    Doggy
    @joedevgee
    I know this is still in Beta, but is there a place for API docs? might be the easiest place to start contributing
    waleedshkt
    @waleedshkt
    Hey guyz, I'm trying to create S3 instance from S3 class in aws-sdk js v3. I add region, accessKeyId, secretAccessKey and sessionToken as constructor config parameters. But I am getting an error saying 'Credential is missing'. Please someone help me out. The issue is opened on stackoverflow at this link https://stackoverflow.com/questions/62612082/credential-is-missing-error-on-instantiating-s3-class-using-aws-sdk-js-v3