ooade / preactsimplestarter

PWA Simple Starter with Preact, Preact-mdl and Webpack2 🔥🔥🔥

Preact Simple Starter

It's highly recommended to use Preact-CLI

PWA Simple Starter with Preact, Webpack 2 and your favorite React related packages 🚀

This App uses:

• Preact
• Preact-mdl
• React-Router
• Redux
• React-Helmet
• Sass
• Webpack Dashboard(For Bundle Analysis)

JS Build files:

• app.js - 78.6kb (17kb gzipped)
• vendor.js - 46.3kb (12.5kb gzipped)

_100/100 on lighthouse 1.4.1 audits_

Quick-Start Guide

• Installation
• Development Workflow

Installation

1. Clone this repo:

git clone https://github.com/ooade/PreactSimpleStarter.git
cd PreactSimpleStarter

2. Make it your own:

rm -rf .git && git init && yarn init

ℹ️ This re-initializes the repo and sets up your yarn project.

3. Install the dependencies:

yarn install

You're done installing! Now let's get started developing.

Development Workflow

4. Start a live-reload development server:

yarn run dev

This is a full web server nicely suited to your project. Any time you make changes within the src directory, it will rebuild and even refresh your browser.

ℹ️ Try to avoid using Service Worker in your development environment, so you won't need to hard reload the page anytime you make a change.

5. Generate a production build in ./build:

yarn run build

You can now deploy the contents of the build directory to production!

License

MIT

preactsimplestarter's Issues

An in-range update of webpack-manifest-plugin is breaking the build 🚨

The devDependency webpack-manifest-plugin was updated from 2.0.3 to 2.0.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack-manifest-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Commits

The new version differs by 5 commits.

• bcca890 2.0.4
• a6e8a2e doc: fix anchor link
• 5e1462b improve functions documentations
• d35b413 upgrade dependencies
• 3aefada chore(package): upgrade to [email protected] (#163)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

docs for customisation

docs for customisation of pwa app.

An in-range update of sinon is breaking the build 🚨

Version 2.3.5 of sinon just got published.

Branch	Build failing 🚨
Dependency	sinon
Current Version	2.3.4
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As sinon is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Release Notes

Fix: Check configurable on a prop before creating

• Check configurable on a prop before creating (fixes #1456) (#1462)

Commits

The new version differs by 8 commits.

• 33f32ac Update docs/changelog.md and set new release id in docs/_config.yml
• d00ab2b Add release documentation for v2.3.5
• 1c690aa 2.3.5
• cc0a3fb Update Changelog.txt and AUTHORS for new release
• ef2ecec Check configurable on a prop before creating (fixes #1456) (#1462)
• e7dbfd7 Merge pull request #1460 from gj/patch-1
• 512018f Fix minor typos
• d60d4a2 Fix apostrophe typos (#1454)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Add test

Create a package for PreactSS configs

I plan on making it simpler i.e having a package that has the necessary configurations to bootstrap the app cos' webpack config scares people a lot 😅

An in-range update of eslint-plugin-import is breaking the build 🚨

Version 2.4.0 of eslint-plugin-import just got published.

Branch	Build failing 🚨
Dependency	eslint-plugin-import
Current Version	2.3.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-plugin-import is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Commits

The new version differs by 10 commits.

• 44ca158 update utils changelog
• a3728d7 bump eslint-module-utils to v2.1.0
• 3e29169 bump v2.4.0
• ea9c92c Merge pull request #737 from kevin940726/master
• 8f9b403 fix typos, enforce type of array of strings in allow option
• 95315e0 update CHANGELOG.md
• 28e1623 eslint-module-utils: filePath in parserOptions (#840)
• 2f690b4 update CI to build on Node 6+7 (#846)
• 7d41745 write doc, add two more tests
• dedfb11 add allow glob for rule no-unassigned-import, fix #671

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

UI / UX

how to build UI / UX for the pwa app. Any docs ?

An in-range update of sinon is breaking the build 🚨

Version 2.3.0 of sinon just got published.

Branch	Build failing 🚨
Dependency	sinon
Current Version	2.2.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As sinon is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Release Notes

Feature: stub accessors in sandbox

• Allow stubbing of accessors with and without sandbox (#1416)
• add throwsArg(index) to stubs (#1319)
• Fix: forEach() requires 'this' argument (#1356)
• Only reset history when calling resetHistory()

Commits

The new version differs by 34 commits.

• 64d51be Update docs/changelog.md and set new release id in docs/_config.yml
• d4b30b0 Add release documentation for v2.3.0
• 8d64248 2.3.0
• e137139 Update Changelog.txt and AUTHORS for new release
• 55dc491 Merge pull request #1416 from lucasfcosta/refactor-sandbox-stub
• fb514cf Merge pull request #1415 from mroderick/style-improvements
• 06bf652 Merge pull request #1414 from mroderick/add-related-libraries-to-how-to-page
• 746de3f Force fenced code blocks to use smaller font
• 1602e00 Improve styling of h4
• 46fd81b Remove deprecation warning from tests for old API
• 454e0fd Add missing final dot to sandbox docs
• 0ea3e17 Add docs for stub.value
• c89fb21 Deprecate stubbing sandbox value in favor of value behavior
• dbefd45 Name restore function on stubNonFunctionProperty
• fe3b9ac Add related libraries section to How To page

There are 34 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Support Server Side Rendering

Incorrect Peer dependency

yarn install got this errors

An in-range update of postcss-cssnext is breaking the build 🚨

Version 2.11.0 of postcss-cssnext just got published.

Branch	Build failing 🚨
Dependency	postcss-cssnext
Current Version	2.10.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As postcss-cssnext is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

2.11.0

• Added: image-set() support
  (via postcss-image-set-polyfill)
  (#373 - @SuperOl3g)
• Added: new auto-deactivation rule in features map
  (#369 - @Semigradsky)

Commits

The new version differs by 10 commits0.

• ed02dc8 2.11.0
• b6f4796 Fix "Unknow browserslist" error
• 480687c Add browsers for testing new futures
• e7cb40b Merge pull request #369 from Semigradsky/patch-1
• 08dd185 Merge pull request #373 from SuperOl3g/master
• 2ca6df0 Fix failed tests.
• a1f8143 update image-set-polyfill package version
• 4c982cd Added: postcss-image-set-polyfill (#43)
• 5200ff2 Add caniuse-db as peer dependency.
• d3b21c1 Update features-activation-map

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of node-sass is breaking the build 🚨

The devDependency node-sass was updated from 4.9.3 to 4.9.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

node-sass is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes for v4.9.4

Dependencies

• Updated request@^2.88.0 (@Gwerlas, #2496)

Supported Environments

OS	Architecture	Node
Windows	x86 & x64	0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
OSX	x64	0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
Linux*	x86 & x64	0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8**, 9**, 10**^
Alpine Linux	x64	4, 6, 7, 8, 9, 10
FreeBSD 10+	amd64	4, 6, 8, 9, 10
FreeBSD 10+	i386	4, 6, 8, 9, 10

*Linux support refers to Ubuntu, Debian, and CentOS 5+
** Node 8 and 9 are not supported on CentOS 5
^ Only available on x64

Commits

The new version differs by 2 commits.

• 476e11c 4.9.4
• 746759c Upgrade request package to v.2.88

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of preact-router is breaking the build 🚨

Version 2.4.2 of preact-router just got published.

Branch	Build failing 🚨
Dependency	preact-router
Current Version	2.4.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

As preact-router is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 11 commits .

• 1c3141a 2.4.2
• 7b3fd37 Update for Preact 8 (#166)
• d8cefef Fix 'should render a normal link' expectation so that it actually checks the rendered HTML (#162)
• 0f79234 Update README.md
• 66b2c0d pass 'native' attr to bypass anchor handler (#154)
• 063f115 Move button check
• 73739be Make the Route component forward all URL parameters (#145)
• d3f7044 🌲
• aed4a6f adding lazy loading in readme (#144)
• 370fa1f chore(package): update preact to version 7.2.0 (#141)
• f961334 adding module key in package.json (#139)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴