An Elm model (no pun intended!) of the Solar System. Wikipedia has more on the concept of an Orrery.
This project is bootstrapped with Create Elm App.
In the project directory you can run:
Builds the app for production to the build folder.
The build is minified, and the filenames include the hashes. Your app is ready to be deployed!
Runs the app in the development mode.
The browser should open automatically to http://localhost:3000. If the browser does not open, you can open it manually and visit the URL.
The page will reload if you make edits. You will also see any lint errors in the console.
You may change the listening port number by using the PORT environment variable. For example type PORT=8000 elm-app start into the terminal/bash to run it from: http://localhost:8000/.
You can prevent the browser from opening automatically,
elm-app start --no-browserAlias for elm install
Use it for installing Elm packages from package.elm-lang.org
Run tests with node-test-runner
You can make test runner watch project files by running:
elm-app test --watchNote: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time.
Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Elm Platform, etc.) right into your project, so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point, you’re on your own.
You don’t have to use 'eject' The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However, we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
Create Elm App does not rely on the global installation of Elm Platform, but you still can use its local Elm Platform to access default command line tools:
Alias for elm repl
Alias for elm make
Alias for elm reactor