Use es6 import / export in WebPack about sapper-template HOT 8 CLOSED

In that case I'd suggest using https://github.com/standard-things/esm, and loading that file inside your webpack config with

// inside webpack config
require = require('esm')(module);
const config = require('../config.js');

from sapper-template.

Sapper would need to use https://github.com/standard-things/esm, basically. I'm not sure it's justified though — is it really a pain point?

from sapper-template.

For my specific use case, yes. I have a config file that drives dotenv with a bunch of specialized settings, but I had to duplicate it exactly w requires for webpack. So now I have two duplicate config files for es6 and older require...which I have to keep parity for.

from sapper-template.

I don't think I understand, can you ELI5?

from sapper-template.

If I have shared settings or config or other files between the main Sapper app and the webpack config files, it would be nice to use one common es6 import/export language, and not have to duplicate files to meet two standards.

I currently have two config.js files, one for webpack with require statements and one for the main Sapper app with import/export statements. Those two files are in essence exactly the same. I'd like to make one file to rule them all.

from sapper-template.

Huh. Already had esm installed for another thingz, but hadn't realized I could just use it™ out of the box like that for webpack.

I'll give it a try and close this ticket.

from sapper-template.

@arxpoetica we good to close this?

from sapper-template.

I never got around to testing it, but I'll reopen if I run into bumps.

from sapper-template.