Commit graph

2 commits

Author SHA1 Message Date
Dima Gerasimov 12593e1199 update webpack and version 2019-01-05 13:55:22 +00:00
Samuel Simões cc81dd9ba4 Collapse boilerplate in a single commit
First prototype

Added the README

Fixed the hot module replacement

Minor adjustments on readme

Normalizing the env vars and using it capitalized

Added info about the react.js branch

Fix babel transpiling

Using yarn

Removing the babel package, just the babel-core does the job

Using just the dependencies key on package.json

Since it isn't a lib package doesn't matter the separation between
devDependencies and dependencies.

Updating the css-loader

Updating the fs-extra

Moving the utility packages to utils folder

Better description

Adds the license

closes #3

Write the env vars on the bundle file

http://dev.topheman.com/make-your-react-production-minified-version-with-webpack/

Fixs the hot reload setup

Sringifies the env object to define plugin

Uses the webpack html plugin to generate the pages in a less hacky way

Uses the write-file-webpack-plugin

this plugin allows the webpack write on disk all files, even running
with the webserver, which is necessary to the hot reload.

this plugin also help us to remove nasty hacks and expose bundles to
other extension features.

Allows exclude some entry points to be hot reloaded

It's useful for content scripts that can't keep the connection with the
webpack endpoint.

Updates the webpack

Updates the README with instructions about the content scripts

resolves #4

Updates to Webpack 2

closes #8

Expand the DefinePlugin usage

In Webpack 1, the replaced value at compile time by define plugin was placed with
parenthesis, like ({"NODE_ENV":"development","PORT":3000}), now, it not works in
this way, breaking the app.

So, to simplify the things, this commit just passes the NODE_ENV var.

Fix README

Exclude /node_modules/ from babel and css transpiling #9

Source maps to help debugging

closes #10

Removes the forbidden webpack config 'chromeExtensionBoilerplate'
before build and webserver's start

Although I know that it's not a good practice, right now I don't know a
good way to keep the boilerplate configs simple as it is today without
this hacky solution, so, until we came with a better solution, we'll
remove the key before build and webserver's start.

  #9

Update README.md

Removing babel.js

Basically, we don't need transpiling with babel since Webpack 2 take care of
ES6 modules transpiling and the ES2015 is supported by Chrome.

  kudos @gagarine

  resolve #16

Setup boilerplate to load images and other assets in html and css

resolves #18
resolves #23
resolves #14
resolves #12

Added icons and images boilerplate

Split dependencies on package.json

resolves #15

Webpack config improvements (#26)

- Use CopyWebpackPlugin to generate `manifest.json` file
- Use CleanWebpackPlugin to clear build folder

Minor README adjustments

* explicitly the required node version
* pointing to yarn install instructions page instead suggest install
with npm. the yarn page will be always updated to the best way to install
the yarn.

closes #28

Adding the contribution guidelines
2019-01-05 10:17:50 +00:00