Getting toastr npm to play with webpack

app.js

import * as Toastr from 'toastr';
import './/../node_modules/toastr/build/toastr.css'; //You need style and css loader installed and set

Toastr.options.timeout = 2000; //Change the settings

Toastr.info('This works!');

Webpack and toastr

//In case anyone was having the same issue in getting toastr to run with webpack and es6

webpack.config.js

var webpack = require('webpack');
var path = require('path');
var assetsPath = '/assets/javascript';
var destinationPointPath = '/dist';
// Why use ProvidePlugin and externals: http://stackoverflow.com/a/30587246/1771644
module.exports = {
    
    entry: `${__dirname}` + '/javascript/src/app.js',
    output: {
        path: `${__dirname}`+ '/dist',
        filename: 'co.js'
    },
    resolve :{
        extensions: ["", ".js"]
    },
    externals: {
        "jquery": "jQuery"
    },
    module: {
        loaders: [
            {
                test: /\.css$/, loader: 'style-loader!css-loader'
            },
            {
                test: /\.js$/, loader: 'babel',
                exclude: /(node_modules|bower_components)/,
                query: {
                    presets: ['es2015']
                }
            }
        ]
    },
    plugins: [
        new webpack.ProvidePlugin({
            $: "jquery"
        })
    ] 
}

FYI according to WebPack documentation "loaders" is becoming extinct in favor of "rules"

Also I was so happy to find this gist but I just cannot get this to work. Granted it's a little funky from the asp prerendering and hot module reloading stuff that came with my boilerplate. But bootstrap and bootstrap.css are working alongside it - why won't toastr??

E: that code snippet is honestly too large and strange to post. Frustration though. Maybe something due to my webpack upgrade to v3.

Great Gist, thank you!

Just fyi the timeout option is labeled timeOut