javascript - Error on sst deploy Your sst.config.ts has top level imports - this is not allowed - Stack Overflow

admin管理员组

文章数量:1352133

Im upgrading from SST 3.2 to 3.11 but as soon as I use the deploy command, I get the following error: Your sst.config.ts has top level imports - this is not allowed. Move imports inside the function they are used and do a dynamic import: const mod = await import("./mod")

This is my old .config file:

import { settings } from 'path/to/settings';

const type = 'test';

export default $config(settings(type));

I have tried to change the config file like this:

const type = 'test';

export default $config(async () => {
  const { settings } = await import('path/to/settings');
  return settings(type);
});

But I get this error Unexpected error occurred. Please run with --print-logs or check .sst/log/sst.log if available. with an empty log folder.

I have tried to search for documentation on this but I have not been able to find anything. Has anyone experienced something similar when upgrading?

Im upgrading from SST 3.2 to 3.11 but as soon as I use the deploy command, I get the following error: Your sst.config.ts has top level imports - this is not allowed. Move imports inside the function they are used and do a dynamic import: const mod = await import("./mod")

This is my old .config file:

import { settings } from 'path/to/settings';

const type = 'test';

export default $config(settings(type));

I have tried to change the config file like this:

const type = 'test';

export default $config(async () => {
  const { settings } = await import('path/to/settings');
  return settings(type);
});

But I get this error Unexpected error occurred. Please run with --print-logs or check .sst/log/sst.log if available. with an empty log folder.

I have tried to search for documentation on this but I have not been able to find anything. Has anyone experienced something similar when upgrading?

• javascript
• typescript
• amazon-web-services
• sst

Share Improve this question Follow edited Apr 1 at 3:53 Phil 165k2525 gold badges262262 silver badges267267 bronze badges asked Apr 1 at 3:06 SantamouSantamou 11511 silver badge99 bronze badges 2

• Never tried SST. Static import is hoisted. Dynamic import() is not hoisted. What happens when you do something like this let fn = async () => { const { settings } = await import('path/to/settings'); return settings(type); }; let result = fn(); export default $config(result); - that is making sure that dynamic import() is executed and there is a result before export? – guest271314 Commented Apr 1 at 3:24
• What sort of result does your settings() function return? Can you give an example? – Phil Commented Apr 1 at 3:52

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 1

Have a look at the reference docs for sst.config.ts.

The $config function doesn't accept a function, instead it wants an object conforming to the Config type with app, run and console properties.

Looks like app is the right callback to use for configuration however what you use depends on the return type of settings().

For example...

/// <reference path="./.sst/platform/config.d.ts" />

const type = 'test';

export default $config({
  // Your app's config
  async app(input) {
    const { settings } = await import('path/to/settings');
    const { app } = settings(type);
    return app(input);
  },

  // Your app's resources
  async run() {
    const { settings } = await import('path/to/settings');
    const { run } = settings(type);
    return run();
  },
});

本文标签： javascriptError on sst deploy Your sstconfigts has top level importsthis is not allowedStack Overflow