cp .env.example .env
)~/.huskyrc
file/_nuxt-content-module-demo
directory if you don't need itnuxt.config.js
package.json
's name and description properties. This info will end up in manifest.json
created by @nuxtjs/pwa
's manifest module.dependabot.yml
# use specified node version
$ nvm use
# install dependencies
$ yarn install
# serve with hot reload at localhost:3000
$ yarn dev
# build for production and launch server
$ yarn build
$ yarn start
# generate static project
$ yarn generate
For detailed explanation on how things work, check out Nuxt.js docs.
Scaffold components and vuex modules:
yarn scaffold
[build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test]
$ yarn commit
to commit with commitizen cli using cz-conventional-changelogIn order to run husky v4+ with Sourcetree one can add a ~/.huskyrc
file.
# ~/.huskyrc
# This loads nvm.sh and sets the correct PATH before running hook
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"
This boilerplate is following the SASS 7-1 pattern.
The architecture consists of:
Note: Not all seven folders of the SASS 7-1 pattern have yet been setup. This is because folders such as /themes
are very project specific.
Add breakpoints to breakpoints.mjs
. Breakpoints are available in SASS, Storybook and @nuxt/image.
sass-mq
Mixin Usage@include mq($from: medium) {
.titanic {
float: none;
}
}
We recommend to use VS Code. Recommended extensions can be installed (prompt by VS Code) when opening the project for the first time. Project settings ensures that linting with eslint
and stylelint
works correctly.
Add with @nuxtjs/storybook. Example config in storybookConfig.js
.