Skip to content

Releases: abiriadev/seia

seia.js@0.1.3

06 Jun 22:03
5b05f10
Compare
Choose a tag to compare

Patch Changes

  • daca655: Fix JSX runtime issue on yarn berry

create-seia-app@0.1.4

06 Jun 22:03
5b05f10
Compare
Choose a tag to compare

Patch Changes

  • 8af865b: Follow up seia.js version

create-seia-app@0.1.3

06 Jun 19:22
2ff262c
Compare
Choose a tag to compare

🎉 We got a new contributor! @fennecfoxsw

Patch Changes

  • 58513d0: Replace unstable APIs with compatible alternative

New Contributors

Full Changelog: https://github.com/abiriadev/seia/compare/create-seia-app@0.1.2...create-seia-app@0.1.3

create-seia-app@0.1.2

06 Jun 09:16
e3e73f5
Compare
Choose a tag to compare

Patch Changes

  • 4b4e0a1: Fix dist not found error caused by manual publishing

create-seia-app@0.1.1

06 Jun 09:08
Compare
Choose a tag to compare

🎉 We got a new contributor!!

welcome to seia, @aidnyu!

What's Changed

  • fix(create-seia-app/ts-template): correct @types/react-dom version to ^18.3.0 by @aidnyu in #18

New Contributors

Full Changelog: https://github.com/abiriadev/seia/compare/create-seia-app@0.1.0...create-seia-app@0.1.1

create-seia-app@0.1.0

04 Jun 05:01
5e3b7f9
Compare
Choose a tag to compare

🎉 We got a new cli tool to create the seia project easily!

Try the below command now!

$ npm create seia-app
$ yarn create seia-app
$ pnpm create seia-app

Minor Changes

  • 1eb70d0: Provide a cli tool to create new seia project

Seia 0.1.2

02 Jun 20:20
Compare
Choose a tag to compare

We got the first contributor! 🎉

What's Changed

  • #6 Thanks @nemorize! - Fixed some typos in codebase and documentations

New Contributors

Full Changelog: v0.1.1...v0.1.2

First release of Seia.js

01 Jun 10:02
Compare
Choose a tag to compare

Seia is now on NPM!

I am pleased to announce that Seia is now available on NPM! 🎉

You can install Seia by running the following command:

$ npm install seia
$ yarn add seia
$ pnpm add seia

Unpublishing Incident on NPM

I inadvertently unpublished version v0.1.0 from NPM to correct a typo in the package.json file. I was unaware that this action would result in a 24-hour block on republishing.

After the block period elapsed, I published an almost identical version as v0.1.1. Consequently, there are no significant differences between v0.1.0 and v0.1.1.

From now on, the version history starts from v0.1.1. 🤣

How Can You Help?

Please consider starring the project on GitHub to enhance its visibility, which helps attract more users.

Additionally, you can contribute by testing the project. Use it and verify if it functions as expected. Check discussion #1 and leave your feedback in the comments!

Thank you for your support! ❤️