Skip to content

Releases: joojscript/phoenix_reactify

alpha-0.0.5

04 Oct 23:11

Choose a tag to compare

Version 0.0.5 is out!

So, recently Phoenix released v1.6.0, and it changed in some ways, how deps are builded and bundled inside the public folder, but as the sample app.js itself says:

// You can include dependencies in two ways.
//
// The simplest option is to put them in assets/vendor and
// import them using relative paths:
//
//     import "./vendor/some-package.js"
//
// Alternatively, you can `npm install some-package` and import
// them using a path starting with the package name:
//
//     import "some-package"

So, basically they kept the support on the old way, and thats great! Because now we can have a more organized package.json, only for react-world dependencies inside the assets folder!

So, here you can check the version 0.0.5 of Phoenix Reactify working:

asciicast

As always, if you want to, there is the binary, compiled version of the library attached to this release, just download it, put inside the root of your Phoenix project, and run!

alpha-0.0.4

10 Jul 01:59

Choose a tag to compare

Version 0.0.4

More like a simple patch

  • new option added: npm_force_install -> was added for noticing in some operating systems, npm had errors for not installing certain dependencies. If this comes to happen, just create a new phoenix project, and run with this option

alpha-0.0.3

30 Jun 19:06

Choose a tag to compare

Version 0.0.3 is out! 🎉

Some major differences:

  • Drop the dependency on CLI Spinners. (It was a nice lib, but unnecessary).
  • Some sample changing on the logs outputted (even the ones without verbose tag).
  • Version checking (very poor yet, but will improve it).
  • Better componentization on source code.

alpha-0.0.2

24 Jun 21:19

Choose a tag to compare

  • Support for typescript
  • Still very unstable
  • New tests will be made

alpha

23 Jun 18:04
2b431b4

Choose a tag to compare

First of all releases, still very unstable, and probably won't work well on every environment, but as tests are being made, and feedbacks are being sent, the library will grow as well.