Skip to content

Releases: Experience-Monks/nextjs-boilerplate

Release 2.7.0

06 Jul 14:21
e5ec17b
Compare
Choose a tag to compare

CHANGELOG

feature

  • node 16

Release 2.6.1

05 Jul 17:59
e5cfc81
Compare
Choose a tag to compare

CHANGELOG

features

  • Added eslint-plugin-sonarjs

Release 2.5.1

29 Jun 04:21
5e7961d
Compare
Choose a tag to compare

CHANGELOG

Fixes and Improvement

  • npm packages version update
  • CookieBanner bug fix in storybook
  • lazy load CookieBanner
  • suppress console in production

Release 2.4.3

16 Jun 11:30
e3363dc
Compare
Choose a tag to compare

CHANGELOG

Fixes and Improvement

  • Improve code readability and maintainability #232
  • Replace typeof window condition with @jam3/detect object #231
  • Fix a bug; FeaturePolicy and ContentSecurityPolicy does not render locally #233

Release 2.4.1

07 Jun 12:23
8c8f9de
Compare
Choose a tag to compare

Changelog

New features

  • SVGO config #195
  • Deploying /storybook route to the develop and staging environment #199
  • Sorting import list automatically #202
  • Default page animtion and gsap registerEffect #204 #207
  • Storybook Welcome page #205
  • Husky post-merge script #216
  • Storybook clean up #218
  • Default https run on localhost #223
  • Add more services and improvements #224

Fixes and Improvement

  • update npm packages #197
  • Docker version change #198
  • Typography #200
  • GSAP init util #201
  • new mixins for breakpoints #212
  • fixes #197

Bug fixes (#182)

Release 2.3.1

23 Nov 14:59
b34e0fd
Compare
Choose a tag to compare

Changelog

New features

  • Next 12
  • New post-build process that converts CSS with alphabetic order for better gzip compression (#181)
  • Progressive Web App (PWA) (#188)
  • Services (#186)
  • Content Security Policy and Feature Policy (#189)

Enhancement

  • Upgrade kusky (#180)
  • Upgrade npm packages (#183)
  • Organize folder structure
    • Move hooks from utils (#184)
    • Move svgs to components from assets (#185)
  • Use next/script for Google Tag Manager script (#187)
  • Lock body scroll service (#192)

Fixes

Release 2.2.1

17 Nov 18:21
1a5b0b5
Compare
Choose a tag to compare

Changelog

New Features

  • GIT LFS in the Codeship (#148)
  • Use .nvmrc and update engines (#168)

Enhancements

  • Implement Seng Generator(by MM) (#133)
  • Introduce new sitemap and robots generator (#171)
  • Organize codeship files (#176)
  • Rename Landing to Home (#154)
  • Update Docker and npm packages (#158)
  • Update ls-lint and add rule for asset files (#177)

Fixes

  • Set default Twitter card type to summary_large_image (#170)
  • Update usage and installation sections in README
  • Fixed linter complaint/issue (#153)
  • Fixed bugs (#150, #162 ,#163, #167)

Release 2.0.5: Cookie Banner and AppAdmin

23 Sep 15:54
d706a81
Compare
Choose a tag to compare

Changelog

  • Add CookieBanner (#144)
  • Add AppAdmin (#131)

Release 2.0.4: NextJS + Typescript

21 Sep 19:41
06b8166
Compare
Choose a tag to compare

Changelog

  • NextJS + Typescript (#132)

  • integrate newer version of @jam3/detect (2.0.5) and removed src/utils/detect
    After working with NextJS, @jam3/detect (1.0.0) was a bit troublesome due to NextJS build options; so had to adapt window type check. The @jam3/detect (2.0.0) now has a built-in window type check gracefully. Doing so src/utils/detect is removed. As a result, detect can be imported from the node module now and selectively imported as it needs.

import detect from '@jam3/detect';
import { os, browser, device } from '@jam3/detect';
  • Absolute imports and Module path aliases (#69)
    Now both relative import and absolute import with a prefix @ alias are available when importing local modules. Absolute importing would be a favourable feature when digging too many depths of folders.
// relative import
import ComponentName from '../../../components/ComponentName/ComponentName';

// absolute import
import ComponentName from '@/components/ComponentName/ComponentName';
  • Improve Template scripts (#140)
    Previously the template script was able to provide a single page/component creation per command and only a single depth. The newer version you can create a multiple page(s)/component(s) with a single command by just listing their name. In addition to that, the script will be able to create children page(s)/component(s) by adding a slash between names.
// create page(s)
npm run page [page-name 1] [page-name 2] ...

// create sub-page(s)
npm run page [parent page-name]/[child page-name]

// create api routes
npm run api [api-name 1] [api-name 2]

// create component(s)
npm run component [component-name 1] [component-name 2] ...

// create sub-component(s)
npm run component [parent component-name]/[child component-name]