Skip to content

Commit

Permalink
chore: switch from yarn to npm
Browse files Browse the repository at this point in the history
We normally use yarn, but as this project is becoming more popular, it seems like an unwarranted extra step for people to get the right version of yarn.
  • Loading branch information
hatton committed Apr 17, 2023
1 parent b010b39 commit d31e6c5
Show file tree
Hide file tree
Showing 6 changed files with 12,610 additions and 8,845 deletions.
4 changes: 2 additions & 2 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -16,9 +16,9 @@ jobs:
with:
node-version: lts/*
- name: Install dependencies
run: yarn
run: npm install
- name: Build
run: yarn build
run: npm run build
- name: Release
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
Expand Down
3 changes: 1 addition & 2 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -4,5 +4,4 @@ sample_img/
i18n/
node_modules/
version.json
docs/
yarn-error.log
docs/
2 changes: 1 addition & 1 deletion docu-notion.config.ts
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
/* This file is only used when testing docu-notion itself, not when it is used as a library.
E.g., if you run `yarn pull-test-tagged`, docu-notion will read this file and use it to configure itself,
E.g., if you run `npm run pull-test-tagged`, docu-notion will read this file and use it to configure itself,
using these example plugins.
*/

Expand Down
Loading

0 comments on commit d31e6c5

Please sign in to comment.