		{
		"name": "phaser-glsl-loader",
		"version": "0.0.1",
		"version": "0.0.2",
		"description": "A shader loader for webpack that allows you to keep your glsl files external when working in phaser.",
		@@ -5,0 +5,0 @@ "main": "index.js",

README.md

		#Phaser GLSL Loader

		[![Build Status](https://travis-ci.org/the-simian/phaser-glsl-loader.svg)](https://travis-ci.org/the-simian/phaser-glsl-loader)

		[![Coverage Status](https://coveralls.io/repos/the-simian/phaser-glsl-loader/badge.svg?branch=master)](https://coveralls.io/r/the-simian/phaser-glsl-loader?branch=master)

		[![Code Climate](https://codeclimate.com/github/the-simian/phaser-glsl-loader/badges/gpa.svg)](https://codeclimate.com/github/the-simian/phaser-glsl-loader)


		[![David-Dm](https://david-dm.org/the-simian/phaser-glsl-loader.svg)](https://david-dm.org/the-simian/phaser-glsl-loader)


		This is a simple GLSL loader that is meant to work with Phaser and Webpack.


		##The Problem:

		Lets say you're working in phaser, and you see a really cool looking fragment shader you want to use.
		@@ -74,2 +89,4 @@

		## The Solution

		First, you need to add the loader to your list of loaders, most likely in your `webpack.config.js` file.
		@@ -99,3 +116,3 @@
		```
		Then you'll be able to reference external files, instead of basically including a large disgusting array of strings!
		Then you'll be able to reference external files, instead of basically including a large array of strings!

		@@ -102,0 +119,0 @@

phaser-glsl-loader - npm Package Compare versions

New alerts