Adds prototypeEntry
config property and --use-prototype
CLI flag. These allow a user to add files from any number of additional entry points to HMR or load them in an additional <script>
(for dev
and production
respectively).
Also:
bodyClasses
config property to supply classes to <body>
for all prototypesThis release includes:
dev
and build
(example: prototype sample images)process.exit()
was exiting too early, preventing webpack build from finishing.Also includes a variety of code cleanup, standardization, and steamlining:
output.library
and output.libraryTarget
(woohoo!). This unifies the dev experience for both the CLI and the browser scriptprebuild
script (which used eslint cli) in favor of eslint-loader
now that we're using webpack for both buildsbabel-preset-env
to latest lts
versionpostbuild.js
in favor of dist/cli/index.js
so cli will still work with dev build. Postbuild was previously prepending the required #!/usr/bin/env node
. However, this was not happening when you ran npm run dev-cli
, so dev-cli
was rather pointless. This creates an index.js
file for use as the npm bin.include
everywhere we're using indexOf
import
for everything we're able to in the CLIgaze
logic to a separate fileWatcher.js
package-lock.json
engines
to package.json to specify both node and npm version requirementscrypto
for the hash, which was adding a whole crapload of modules to the browser build.index.js
for both web and cli entry pointsopn
would open a prototype URL with doubled slashes after the configured root
directory if user added a trailing slash in their configuration. This fix removes any trailing slashes that may be there.
Linting wasn't actually functioning in the last beta release, this release fixes it.
This release settles on a method of both transpiling and linting browser HMR logic.
Also includes:
babel-preset-env
to latest lts
versionpostbuild.js
in favor of dist/cli/index.js
so cli will still work with dev buildinclude
everywhere we're using indexOf
import
for everything in the CLIgaze
logic to a separate fileWatcher.js
package-lock.json
crypto
for the hash, which was adding a whole crapload of modules to the browser build.index.js
for both web and cli entry pointsprebuild
script (which used eslint cli) in favor of eslint-loader
now that we're using webpack for browser build alsoInstalled jest and added a few starter unit tests. Test away!
First pass at setting up jest
and writing some tests!
This release will add support for huron function configs, similar to the same implementation in webpack 2. This means you'll be able to provide flags like --env.production
on the command line (or in an npm script) and { production: true }
will be passed into your huron configuration function. More information on how to use this in webpack can be found here, and the same function(env) { ... }
pattern can now be used in huron as well.
Webpack 2 allows you to pass a function that returns your config object, instead of supplying the config object directly. This release adds support for using a webpack function config (including the --env
flag).
HTML webpack plugin was referencing a non-existent location for its template when user includes a context
property in the webpack config. This changes the path to the template to be absolute.
Also includes a couple updates for the internal webpack build.
This release passes on Webpack compile errors when running the production build, making errors easier to debug.
This release addresses several issues:
npm install
tested and fully functional, including bundled huron
binary.Note: I accidentally published version 2.1.0
on the beta
tag in NPM, so I wasn't able to publish over it in the latest
tag. I've bumped the version straight to 2.1.1
to accommodate this (I'm still getting used to this!)
Didn't know we needed to include #!/usr/bin/env node
at the top of the binary, wrote a small postbuild script to prepend it after the build is complete.
This release includes rewrites necessary for migration to Webpack 2. Since Huron has so few users thus far, we are not supporting backwards-compatibility with Webpack 1, and thus bumping the version up to 2.0.0.
Major changes:
Safari doesn't like dataset so much, so I added fallbacks for our usage of that property.
This is the official public release of version 1.0.0, which contains a range of significant, breaking updates in the overall structure of how Huron functions. Some highlights: