Edge, IE11 broken. Invalid bundling and exports.

Currently bundling for Webpack environments / module environments is broken. In the Webpack build the library is build and transpiled - although in package.json it only points to the root (unstranspiled) /wpapi.js file. This is okay for most modern browsers as - only by chance - the features are supported.

Although this is not the case for Edge and IE11 both not supporting the object rest spread operator.

In summary the build is essentially broken for browsers environments - node works.

This long standing issue: https://github.com/WP-API/node-wpapi/issues/426 outlines the case with specific errors.

[andrewmclagan]

Workaround for those Webpack / bundler users who want support for Edge and IE 11 you can simply add the “browser” bundle (umd) as an external dependancy. Bundling it via package.json (node_modules) will break your build in IE and Edge.

Webpack e.g.

/**
 * Webpack config object
 * @return {Object}
 */
module.exports = (env, argv) => {
    // ...
    externals: {
      wpapi: 'WPAPI'
    },    
    // ...
};

Then import as usual:

import WPAPI from "wpapi";

😦

My suggestion to the authors would be to write the library in ES then transpile to CJS and UMD. That way we are working from best case to worst case, smallest footprint.

[nsundberg]

Workaround for those Webpack / bundler users who want support for Edge and IE 11 you can simply add the “browser” bundle (umd) as an external dependancy. Bundling it via package.json (node_modules) will break your build in IE and Edge.

If you want to avoid editing the Webpack config and/or including it using a script tag you can also import the browser bundle directly:

import WPAPI from 'wpapi/browser/wpapi.min';