mcansh / next-boilerplate

Next.js Boilerplate

Quickly start a new nextjs project

Usage

1. Click that fun 'Use this template' by the clone button
2. Update package.json and manifest file
3. Build awesome shit

next-boilerplate's Issues

Nice work

Hey Logan @mcansh , I recently started a new Next.js and decided to use a template to find new work flows and ways to do things.

I picked yours and after the initial burden of having to configure the linting rules to match my level of caring enough (also had to remove the Github hosted npm packages since they didn't work very smoothly), I'd say I'm quite positively surprised.

The style linter especially was a welcome addition as it actually found good suggestions.

Also I've been very wary of service workers after being bit in the ass a couple of times yet it seems in this case work quite fine. It does boost page loads nicely.

There might have been some small enhancements that I've done but forgot about. At least one major change I would do is remove node 13 from the Github action testing matrix since it fails automatically with postcss library. Also I added dark mode which now works quite well. Dunno if you are interested in incorporating such thing into your template. I can show how I at least did it (and you can point out if there's something wrong with it). My repo is btw private so you won't find in my profile.

But anyway - thanks. I guess I could get used to this boilerplate for my future Next.js projects.

Teemu

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 🌴

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

The dependency esm was updated from 3.0.82 to 3.0.83.

🚨 View failing branch.

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

esm is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

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 73 commits.

• 82f4a8d Bump to v3.0.83.
• c7d1225 Add ESM_DISABLE_CACHE to readme.
• 9339890 Add ext priority test for options.cjs.paths.
• 85cd3c1 Remove unused assert import from ext tests.
• b73ca44 Destructure error code in tests.
• ab1aba5 Make ext tests use the actual ext.
• 04e567c Cleanup Entry#addGetterFrom(), Runtime.addExportFromSetter(), and Runtime.addNamespaceSetter().
• 0d7117c Remove ERR_MODULE_RESOLUTION_LEGACY guard from makeRequireFunction().
• e980f7d Remove isError() and options.cjs.paths guard from tryParse().
• 608a625 Minor format Entry format nits.
• ea100b1 Remove isError() guards for errors coming from esm/validate.
• 38accbe Use Map for the stat cache.
• 4419e2d Minor dummyProxy class cleanup.
• 96c8257 Use maps for memoize caches.
• d0a33f6 Ensure .cache folder is cleared before the first test run.

There are 73 commits in total.

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 🌴