workerize External deps

We very often want to use libraries like lodash in compute intensive routines that would be good to run in workers. Have you thought about how to solve this problem?

Jan 12 '18 17:01 alisman

Yup, that's what workerize-loader is for.

Alternatively, it would be pretty easy to add { type: 'module' } to the Worker instance here, which would enable ES Module imports in modern browsers.

Jan 13 '18 20:01 developit

Using ES Modules is now supported in 0.1.5.

It works like this:

import workerize from 'workerize';

const worker = workerize(`
  import fetchJson from './fetcher'

  export function get(url) {
    return fetchJson(url)
  }
`, { type: 'module' });

worker.get('./some-url').then( data => {
  console.log('Response: ', data);
});

Jan 19 '18 15:01 developit

I'm receiving an error when I attempt to implement this feature.

To troubleshoot, I rolled back to version 0.1.5 and attempted to directly mimic the example code:

// fetcher
function fetchJson(url, config = {}) {
    return fetch(url, {
        ...config,
        headers: {
            ...(config.headers || {}),
            'Content-Type': 'application/json'
        }
    }).then(response => response.json())
}

export default fetchJson

And implementing it in a worker:

const worker = workerize(`
    import fetchJson from './fetcher'

    export function get(url) {
        return fetchJson(url)
    }
`, {type: 'module'})

worker.get('https://jsonplaceholder.typicode.com/posts/1').then(data => {
    console.log('Response: ', data)
})

Yields the following error (also logging the worker to the console):