content-api, Typescript & Webpack build fails about sdk HOT 7 CLOSED

I faced the same problem.

As far as I understand the error is related to the fact that a CommonJS module is not imported in compliance with the es6 module spec because an import can only be a plain object and is not callable.

To avoid this problem in typescript the variable esModuleInterop can be set to true in tsconfig.json which removes the error.
esModuleInterop generates helper code to avoid this problem.

@allouis maybe you had esModuleInterop already set in your tsconfig.json? Then it is not reproducible.

I am not sure if the problem also exists if plain es6 (without typescript) is used...

from sdk.

Hey, I tried running your example and Typescript will not compile the code you've posted.

I've replaced it with this and it compiles, and works fine both before and after using webpack.

import * as GhostContentAPI from '@tryghost/content-api';

export function getPosts() {
  const api = new GhostContentAPI({
    url: "http://localhost:2368",
    key: "**************************",
    version: "v2",
  });

  api.posts
    .browse({limit: 5, include: 'tags,authors'})
    .then((posts: any) => {

      posts.forEach((post: any) => {
        console.log(post.title);
      });
    })
    .catch((err: any) => {
      console.error(err);
    });
}

getPosts();

We'll need some easier to reproduce steps to get this solved!

Out of interest, what is the reason for using webpack on serverside code?

from sdk.

@allouis is there anything further to do here or can this be closed?

from sdk.

Can't replicate and no activity - closing :)

from sdk.

@daveKoala did you ever resolve your issue? I'm experiencing similar behaviour.
@allouis my need to use webpack is because I'm compiling an angular app for server-side rendering.

from sdk.

@zpydee I am using the api successfully - I don't remember what i done but if you want me to look let me know and i'll fish the code out

from sdk.

yes please. I am doing a connection from svelte and I need to know how you overcame that as I still am facing issues

from sdk.