starbase

This is an incremental maintenance release:

• All dependencies were updated to their latest versions.
• CSS color variable names have been updated (this one's been bugging me for a while).

This is a small maintenance release, but received a minor release tag because it contains a tweak to the production webpack config, to accommodate an update to a webpack plugin used within it.

Besides that, the other notable change is that css assets are manually imported in /src/app.css instead of automatically imported via require in /src/app.js. The reason for this is that when require is used, it ends up in the production-compiled dist/app.js. To see for yourself, run a production build on the 2.1.0 release and compare to 2.0.2.

Other changes include:

• all dependencies updated
• yarn.lock removed, references to yarn removed from readme

2.0.2 is a hotfix incremental release, which resolves an issue in the 2.0.1 release, involving the update configs needed for clean-webpack-plugin.

2.0.1 is an incremental maintenance release, which tests and applies all currently-available dependency updates.

2.0.0 is a major release, which focuses on simplifying the assets (HTML, CSS & JS) found in the boilerplate. This is being done for a couple reasons:

• getting up and running, as a developer using starbase, will now be quicker because there's less bloat that you have to strip out before getting started.
• starbase is now less opinionated, as all boilerplates should be. This is a tool that is meant to be used as a baseline, not the end-all-be-all of a project, so customization should be facilitated and rules should not be dictated.
• starbase is now easier to maintain, and hopefully easier to fork into even more variants.

Look out for an updated version of starbase-react soon!

2.0.0 Patch Notes

• drastically reduced the amount of CSS & JS found in the boilerplate assets.
• renamed watch command to dev - this was done because it seems to be the norm in 2018/2019 and the theme of this patch is simplifying things (which sometimes means conforming to norms).
• removed postcss-responsive-type plugin - again, it's all about simplification.
• fixed broken source maps when using the dev command
• svgs now end up in /images instead of /assets, to be more consistent with the other image types (png, jpg, jpeg, gif).
• fetch & promise polyfills are now commented-out by default, because they aren't actually used anywhere in the boilerplate assets. the main readme has been updated to notate this change.
• travis ci has been removed from the project, because it really wasn't necessary and it was more of a personal learning experience, than anything actually useful for this project.
• all dependencies updated.

• dependencies updated, notable updates include postcss-preset-env and switching over to the new @babel packages/configs.
• removed auto-injection of variables - this feature was janky (a proprietary, local postcss plugin) and confusing for new users. manually importing variables as you need them results in more-readable and deliberate code.

This is a maintenance release and contains no changes to the structure or flow of the boilerplate, but will be considered a minor release because of the number of major dependency updates it contains.

The highlight of this release is support for Babel 7, but several other dependencies (eslint, PostCSS, etc) also received major version updates.

As of right now, all dependencies are 100% up to date. Enjoy!

postcss-cssnext has been deprecated in favor of postcss-preset-env... so it's time to jump ship!

• replace postcss-cssnext with postcss-preset-env
• dependency updates, including several major version updates
  • eslint was kept back to v4.x because airbnb's preset isn't ready for v5 yet
• slight constructor tweak in the default component js to accommodate new linting rules (from the airbnb preset)
• dev (yarn watch) builds now minify css just like production (yarn build) builds (but with sourcemaps) to avoid build-specific anomalies

• dependency updates (primary motivator of this patch)
• readme.md & package.json verbiage tweaks
• index.html template tweaks/cleanup

nothing fancy. just a quick maintenance release.

1.2.0 is a minor release for starbase that includes a few build tweaks and new features:

• offline-plugin is now used on production builds to provide a service worker that allows return visitors to load your app, even if they have no internet access. This came about from an enhancement request (#41), so a huge thank you to @WebRuin for the great suggestion!

• all asset filenames are now hashed for production builds. Core assets (JS & CSS) receive a new hash for every build, but more stable assets (images, fonts, etc) only receive a new hash when their content changes.

• postcss-extend has been integrated into the build process, and added to the tags component CSS to demonstrate usage. I use this plugin a lot at my day job and it's been sorely missing from starbase.

• lots of additions to the core readme to cover the new features described above, including how to remove/disable the ones that some folks might not like (or want to deal with).

• all dependencies updated to the latest versions

• lots of new README.md files throughout the project
• formatting tweaks to example template (html), no functional changes
• all dependencies updated to latest versions

a quick maintenance release:

• dependency updates (i believe this resolves #38)
• version bump

• resolved #35 (thank you, @AknEp!)
• removed redundant production flag (webpack =>3 relic) from scripts
• dependencies updated
• incremental version bump

• remove some relic assets accidentally left over from 1.0.2 > 1.1.0
• readme update to provide basic coverage for html-webpack-plugin utilization

This is a minor release because it contains many changes to the build process, mostly around how static assets (images & html) are handled.

With webpack 4 being released and used on this project, expect to see many incremental updates in the next few weeks as I do my best to stay up to date on dependencies (who are scrambling to ensure webpack 4 compatibility).

• replaced extract-text-webpack-plugin with mini-css-extract-plugin (a more webpack4-centric plugin).
• no more using copy-webpack-plugin to manage static assets... it's all done with webpack now via html-webpack-plugin and html-loader!
• cleaned up & simplified webpack configs.
• travis integration & other shiny badges.

This is an incremental update that adds support for webpack 4.

If you prefer webpack 3, simply remove webpack-cli and downgrade webpack in /package.json... no further code changes are required.

• first pass at aria accessibility-friendliness
• .no-js on html element, first pass at no-js accessibility
• restructuring (cleaning up) html & css
• dependency updates & version bump

TL;DR - cleaning up the demo page structure to be as clean and accessible as possible. No build system (breaking) changes.

I started this project a year ago primarily as a personal learning tool, but ended up sticking with it and really enjoying maintaining my own devkit/boilerplate. I knew when I started that whatever I built wasn't production-ready, so I gave it a 0.x.x version, but people ended up using it anyways (which I am delighted by).

I've learned a lot over the past year and have been using starbase on various personal projects the whole time-- tweaking the main repo as I thought of things to add, remove or change.

I like the code that starbase produces and think it's time to call it production-ready, so I spent some time this weekend tidying things up and making the index/demo page more marketable and informative and less dev'y.

I'll be updating starbase-wordpress and starbase-react over the next few weeks, to bring them up to speed with the latest goodies.

So here it is... version 1.0.0 -- neat!

• all dependencies updated to latest versions
• readme/documentation updates
• starter components, base styles & index.html rebuilt from the ground up to be more informative and demonstrate usage