ECONNRESET

I’m getting UnhandledPromiseRejectionWarning: Error: read ECONNRESET,

Is there a debug mode so I can understand what’s happening here?

my config file:

module.exports = {
  commands: [
    [
      "components",
      {
        fileId: "XXXX",
        onlyFromPages: ["icons", "illustrations"],
        transformers: [
          require("@figma-export/transform-svg-with-svgo")({
            plugins: [{ removeViewBox: false }, { removeDimensions: true }],
          }),
        ],
        outputters: [
          async (pages) => {
            const output = "./public";
            fs.mkdirSync(output, { recursive: true });
            console.log("OUTPUT", output);
            try {
              pages.forEach(({ name: pageName, components }) => {
                console.log("PAGE", pageName);
                components.forEach(({ name: componentName, svg }) => {
                  const filePath = path.resolve(output, `${componentName}.svg`);

                  let p = filePath.split("/");
                  p.pop();
                  p = p.join("/");

                  fs.mkdirSync(p, { recursive: true });

                  fs.writeFileSync(filePath, svg);

                  console.log("GENERATED", filePath, componentName);
                });
              });
            } catch (e) {
              console.log(e);
            }
          },
        ],
      },
    ],
  ],
};

[marcomontalbano]

Hi @berkaey, thank you for all these details.

I tried by using the same configuration you provided (off-course with a different Figma File) and everything worked properly. For sure I’ve to handle all promise rejection and improve the application log to better understand the root cause.

The error ECONNRESET should be not related to transformers since they just manipulate strings. ECONNRESET is related to a network issue. Figma Export uses the network to connect to Figma Api and to download SVGs. I can also improve the application there to better handle exceptions from Figma.

Rate Limit is for sure another option, I’ll investigate more.

Thanks, I’ll keep you posted.

[berkaey]

Hi @berkaey, I’m going to close the issue since I just release the new version v3.2.0.

I was looking at your configuration file and seems to me that you could replace your custom outputter with @figma-export/output-components-as-svg.

outputters: [
    require('@figma-export/output-components-as-svg')({
        output: './public',
        getDirname: (options) => options.dirname,
    })
]

The option getDirname gives you the ability to change the folder structure when exporting components.

yes I noticed that too, but I also replace some IDs in SVG file so this is why I implemented it like this.