fix import from rds

[fat23cat]

I'm really sorry I made a mistake in the import in the #75 :(

[simonrw]

How did you find this out? The commit I pushed verified both behaviours against AWS and LocalStack and I found that this functionality worked just fine.

[fat23cat]

How did you find this out? The commit I pushed verified both behaviours against AWS and LocalStack and I found that this functionality worked just fine.

I'm using this package to run appsync resolvers unit tests using vitest.
I'm replacing @aws-appsync/utils with your package in the vitest config:

export default defineConfig({
  resolve: {
    alias: {
      "@aws-appsync/utils": path.resolve(
        __dirname,
        "node_modules/appsync-utils"
      ),
      "@aws-appsync/utils/rds": path.resolve(
        __dirname,
        "node_modules/appsync-utils/rds"
      ),
    },
  },
  test: {
    environment: "node",
    include: ["src/**/*.test.{js,ts}"],
    ...configDefaults,
  },
});

But tests are failing:

Error: Directory import '.../node_modules/appsync-utils/rds' is not supported resolving ES modules imported from /...node_modules/appsync-utils/index.js

[fat23cat]

And this is how ES modules work https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules#importing_features_into_your_script

[simonrw]

Thanks for fixing this. I have executed the LocalStack tests locally and confirm that it has not broken anything.

I am interested to understand more. I will be the first to admit that I don't understand the JS module system. I have had problems with this package and not being able to split it up, and to have weird import structures. I would appreciate someone who knows more about JavaScript to help me refactor this.

I will merge this as I trust that the change is correct. Thanks again!