How do I use it with my projects? about reactide HOT 21 CLOSED

The above instructions should be added to README.

from reactide.

1. yarn install
2. yarn dev
3. In another terminal: yarn dev-start

Most electron projects that use webpack also include a script that uses concurrently so the second two steps are the same. I suggest the repo maintainers add such a script.

from reactide.

agreed with @probablyup

v1.0.0 should expose at least a complete readme, and a site with

• presentation
• how to install (win-installer | i didnot find for macOS but there is this Electron packaging page)
• how to run (should implement a one-command-run-it-all, or shortcut on desktop)
• a features page showing how-to with simple examples
• how to debug and run test suites (should replace Mocha/Chai with Jest) THIS is the key feature in my humble opinion making ReactIDE above any other editor, especially state flow visualization. An example with Redux would fit as showcase.
• how to package/build/deploy

Keep in mind there is a commercial concurrent React Studio already much more advanced, with importing Sketch designs capabilities.

Rushing for release would risk to ruin this potentialy nice app...

from reactide.

hey guys, please note the project is still in early development. You can follow the instructions above with yarn or npm to run the current iteration. Cheers!

from reactide.

Taking a day to put together an automated installer / launcher (for macOS at least) would skyrocket the usage of this. Not sure why you folks announced it without one to be honest.

from reactide.

This should be in the readme file...
#60

I'm not sure I understand the logic around "this is early development" so we're going to make people open up package.json and figure out how to run the application or better yet, look at random issues on their own.

But w/e good luck :)

from reactide.

I agree the idea is great but getting started by having to read through the issues is a put off

from reactide.

@imvetri, yes, it's works with npm.

1. npm install
2. npm run dev
3. In another terminal: npm run dev-start

from reactide.

:(

from reactide.

@Sharlaan @probablyup I put out a PR and they closed it saying they dont want it. I think theres an emphasis on keeping just a few devs on this and keeping the hype up. I could be wrong and I'd love to hear otherwise.

from reactide.

Would the same work with npm as well?

from reactide.

@imranmalik: It used to be, but looks like it was removed 4f546d3

from reactide.

I did the same steps

1. yarn install
2. yarn dev (one terminal)
3. yarn dev-start (another terminal)

what am I supposed to see? a todo app? it doesn't show anything?
I get the electron window with the file tree but theres nothing showing up.

from reactide.

@codingphasedotcom I'm getting the same bug/errors.

from reactide.

why it not GUI?

from reactide.

I'm having the exact same issue as @codingphasedotcom. I can start reactide but then nothing shows in the main panel.

Thanks for your hard work so far I'm looking forward to being able to use this with a project soon

from reactide.

@codingphasedotcom I'm having the same problem when I run npm run dev in a terminal and run npm run dev-start in another terminal .

from reactide.

The project is still in its early stages. There will be detailed instructions on setting up the development environment in the next few days. Thanks!

#35

from reactide.

Can we add the starting instruction to README.md? Took me a while to find this information.. almost abandoned this repo.

from reactide.

Does the simulator button do anything? I only get a blank simulation of HTML page. Doesn't see any React component being rendered 😢

Also, I'd suggest moving the Simulator button to bottom right.. make it green and much bigger (perhaps a play button as well.) It's a small UX change but if everyone is going to hit that button.. it's VERY important to make it right.

from reactide.

This isn't really an open project so you guys trying stuff under the hood may not be how the backend or anything else for this is setup. There's no readme documentation intentionally because they dont intend it to be public.

from reactide.