awesome-webpack | curated list of awesome Webpack resources | Awesome List library

It turned out that Angular Material 1.1.10 interfere with fullcalendar. It overrides touch handling in some way. And event is recognized as mousedown instead of touchstart.

Solution is to remove all pointer events from:

The official documentation says to write rule for loading of less files like this:

This is actually not solved by me but by @kittaakos ( guys who have created this awesome platform theia)

So, to summarize :

1. Make sure your VM has enough RAM like 4 GB.. It might even work with 2 GB. So, if you are getting exit code 137; try upgrading RAM.
2. It works like a charm on Node.js 8.11.4
3. By default it starts on localhost for security considerations. If you want it to be exposed via external IP; use

$ yarn run start --hostname 0.0.0.0

It seems you need to include a loader for .css in your webpack configuration:

I tried with your code and use the file jquery-jvectormap-world-mill-en I get from github. But it seem working fine. Could you provide also your package.json?

EDIT: Try to remove options: { presets: ['es2015']} If you don't use ES6. If you want to use babel to transform, try to follow babeljs.io/docs/plugins/#presets

Hopefully this will point you in the right direction even though its not a complete solution. As I mentioned I spent a ridiculous amount of time trying to get Semantic-UI working with Webpack 2. I'm using the Webpack template from vue-cli for a VueJS project. I tried stripping the Vue configuration out of the template to get an example that was framework agnostic but that didn't go well.

It looks like you might just be trying to get Semantic-UI CSS setup, and not their JS components. All the additions I made to the Vue Webpack template are related to JS, basically just to include jQuery for Semantic-UI. So if you're only interested in getting the CSS working these additions aren't necessary.

In order to get the template's configuration to work with Semantic-UI JS, I added this to module-exports

FYI solution is:

webpack config file:

The outputPath option in the file-loader is relative to your output directory and therefore will be included in the path. And publicPath just adds the given path to the beginning of the used paths, it basically means that the output directory will be located somewhere else on the server. This leaves the original path unchanged, since the structure within the directory must be unchanged.

To make it work as you described, you need to change how you handle the output directory. As you've already mentioned your output directory is www, that's where webpack should put everything. Therefore it makes sense to configure output.path to www.

So I solved this thing using webpack's resolve.alias functionality with dynamically added filenames into it. Here's the code: