Unverified Commit 35f1b262 authored by Christopher Guindon's avatar Christopher Guindon Committed by GitHub
Browse files

update solstice and switch to yarn (#235)


Signed-off-by: Christopher Guindon's avatarChristopher Guindon <chris.guindon@eclipse-foundation.org>
parent 01411c27
install:; npm ci
build: install; npm run build
install:; yarn install --frozen-lockfile
build: install; yarn run build
run: build; hugo server -s exampleSite --themesDir=../..
clean:;
rm -rf node_modules
rm package-lock.json
rm yarn.lock
release: clean;
npm install
npm run production
yarn
yarn run production
git add .
git commit -m "prepare new release" -s
\ No newline at end of file
install:; npm ci
build: install; npm run build
install:; yarn install --frozen-lockfile
build: install; yarn run build
run: build; hugo server -s exampleSite --themesDir=../..
clean:;
rmdir node_modules
rm package-lock.json
rm yarn.lock
release: clean;
npm install
npm run production
yarn
yarn run production
git add .
git commit -m "prepare new release" -s
\ No newline at end of file
......@@ -22,12 +22,12 @@ Install dependencies, build assets and start a webserver:
make run
```
To run npm watch and hugo server at the same time:
To run yarn watch and hugo server at the same time:
In one terminal:
```bash
npm run watch
yarn run watch
```
Once above process is done, in another terminal:
......@@ -49,7 +49,7 @@ set NODE_ENV=production && npm install
Install [win-node-en](https://github.com/laggingreflex/win-node-env) globally and then install our dependencies by following the steps from our [Getting Started](https://github.com/EclipseFdn/hugo-solstice-theme#getting-started) section.
```bash
npm install -g win-node-env
yarn add -g win-node-env
```
### Known Issues
......
This source diff could not be displayed because it is too large. You can view the blob instead.
......@@ -24,7 +24,7 @@
"readmeFilename": "README.md",
"dependencies": {
"axios": "^0.21.1",
"eclipsefdn-solstice-assets": "0.0.160",
"eclipsefdn-solstice-assets": "0.0.162",
"json2yaml": "^1.1.0",
"parse-link-header": "^1.0.1",
"toml": "^3.0.0"
......
This source diff could not be displayed because it is too large. You can view the blob instead.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment