Not able to use JavaScript SDK in Angular 8

Girish_Nalawadi · August 19, 2019, 5:31am

Hi,
I have generated an Angular application using Angular CLI and installed the pure cloud library using npm. I am not able to import platformClient or the module.
Request anybody if they have used javasrcipt SDK in angular application to give some tips on using Pure cloud JS SDK in Angular CLI application.
I know there was a request in this earlier, but I am not able to follow the suggested changes: https://developer.mypurecloud.com.au/forum/t/unable-to-use-js-sdk-in-angular-7-web-app/5086

tim.smith · August 19, 2019, 1:52pm

That thread you linked has the correct instructions. You need to configure your compilation tool (e.g. webpack) to make it use the jsnext:main entry point to access the es6 source classes instead of the pre-compiled modules. The pre-compiled modules have been created for use in CommonJS (node/web) and AMD (require.js) applications. Any situation where you're doing your own compilation requires you to reference the es6 source classes so they can be transpiled into your app appropriately.

Girish_Nalawadi · August 21, 2019, 2:52am

Hi Tim,
Angular CLI project is different from the React project. I am not able to find the web pack config you are referring above.
Regards,
Girish

tim.smith · August 22, 2019, 2:19pm

github.com

MyPureCloud/platform-client-sdk-javascript-beta/blob/master/examples/react/config/webpack.config.dev.js#L72


  // There are also additional JS chunk files if you use code splitting.
  chunkFilename: 'static/js/[name].chunk.js',
  // This is the URL that app is served from. We use "/" in development.
  publicPath: publicPath,
  // Point sourcemap entries to original disk location (format as URL on Windows)
  devtoolModuleFilenameTemplate: info =>
    path.resolve(info.absoluteResourcePath).replace(/\\/g, '/'),
},
resolve: {
  // This allows webpack to choose the ES6 source code from the jsnext:main property in the SDK's package.json
  mainFields: ['jsnext:main', 'browser', 'module', 'main'],


  // This allows you to set a fallback for where Webpack should look for modules.
  // We placed these paths second because we want `node_modules` to "win"
  // if there are any conflicts. This matches Node resolution mechanism.
  // https://github.com/facebookincubator/create-react-app/issues/253
  modules: ['node_modules', paths.appNodeModules].concat(
    // It is guaranteed to exist because we tweak it in `env.js`
    process.env.NODE_PATH.split(path.delimiter).filter(Boolean)
  ),
  // These are the reasonable defaults supported by the Node ecosystem.

Anders_Vejen · September 2, 2019, 8:15pm

See this explanation on how to get it to work.

system · October 3, 2019, 8:16pm

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.