From f8141401bf0903f32c2f83029a136c5c2d9353b1 Mon Sep 17 00:00:00 2001 From: Valist Bot Date: Mon, 12 Jun 2023 02:55:24 +0800 Subject: [PATCH 1/3] Add Valist publish workflow --- .github/workflows/valist.yml | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 .github/workflows/valist.yml diff --git a/.github/workflows/valist.yml b/.github/workflows/valist.yml new file mode 100644 index 0000000..48d19b5 --- /dev/null +++ b/.github/workflows/valist.yml @@ -0,0 +1,34 @@ +name: Valist Deploy +on: + push: + branches: + - main +jobs: + build: + runs-on: ubuntu-latest + steps: + - name: Checkout + uses: actions/checkout@v3 + + - name: Setup Node + uses: actions/setup-node@v3 + with: + node-version: '16' + + - name: Build and export Next.js app + run: | + npm install + npm run build && npx next export + + - name: Mark Timestamp + run: echo "TIMESTAMP=$(date +%Y%m%d%H%M)" >> $GITHUB_ENV + + - name: Valist Publish + uses: valist-io/valist-github-action@v2 + with: + private-key: ${{ secrets.VALIST_SIGNER }} + account: ricy + project: ricysdemohouse + release: ${{ env.TIMESTAMP }} + platform-web: out + \ No newline at end of file From bbab61ac475cea51d61a5842434d50a06f68425a Mon Sep 17 00:00:00 2001 From: Ricy <97211928+Ricy137@users.noreply.github.com> Date: Sun, 2 Jul 2023 22:10:16 +0800 Subject: [PATCH 2/3] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f5424e9..d390767 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ ## Why do I start the repo? -React components libraries like MUI is a good option for fast development phase, but they're also large and hard to customize. So I developed custom-ui since a customized component library will provide the minizest size which is good for performance, it will also be much easier for me to customize these components as well as optimize them and it would be a good way to level up my skills as a frontend engineer. +React components libraries like MUI, ANTD is a good option for fast development phase, but they're also large and hard to customize. So I developed custom-ui since a customized component library will provide the minizest size which is good for performance, it will also be much easier for me to customize these components as well as optimize them and it would be a good way to level up my skills as a frontend engineer. But work is stressful and in high speed. Fortunately, I managed to get some optimization time for a project and successfully replaced all the MUI components with self made components in that project, which recuded almost 20% of overall JavaScript bundle size (of course which also leads to better performance). I decided to make more advantages of these components and make them more reusable, so I started this repo. From 586d0052f6cb467dab5d812da8c7262770c7e9b7 Mon Sep 17 00:00:00 2001 From: Ricy <97211928+Ricy137@users.noreply.github.com> Date: Sun, 13 Aug 2023 23:07:49 +0800 Subject: [PATCH 3/3] Update README.md --- README.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index d390767..0dc26e9 100644 --- a/README.md +++ b/README.md @@ -11,4 +11,9 @@ But work is stressful and in high speed. Fortunately, I managed to get some opti ## Conflicts and thoughts Next: I love Next, the server side rendering is a great way to improve performance, its optimiztion for images is great, turboPack... But of course, due to Next's SSR feature, I also met many conflicts. -One of the conflicts I met is UnoCSS which is an alternative to TailWind. UnoCSS can not only provide better performance and flexsibility, but also released more potention of Atom CSS : https://antfu.me/posts/reimagine-atomic-css . However, while I'm having a good time with UnoCSS with React and Vite, I didn't find a good to use it seamlessly with Next :( + +One of the conflicts I met is UnoCSS which is an alternative to TailWind. UnoCSS can not only provide better performance and flexsibility, but also released more potention of Atom CSS : https://antfu.me/posts/reimagine-atomic-css . However, while I'm having a good time with UnoCSS with React and Vite, I didn't find a good to use it seamlessly with Next :( . Current UnoCSS CLI is used. + +## Future plan +- add PWA features +- add documents and examples