You need at least npm@5 (bundled with node 8) because of its
npm install <local-path> creating symlinks.
Works in Windows as well, trying junctions and/or true symlinks, so no fear.
Amber repository contains more parts:
lang/directory). This is released.
cli/subdirectories). They have their own release track.
Gruntfile.jsand its friends). Not part of release.
To get your clone, follow this list:
npm install -g @ambers/cli.
npm installto install dependencies listed in package.json. Used by development tools. See here for more info.
cd lang && npm install && cd ..to install dependencies of
cd sdk && npm install && cd ..to install dependencies of
<project-path>/helios, choosing among using your own fork / using the stock version:
git clone firstname.lastname@example.org:<your username>/helios.git ../heliosto use your own fork, or
git clone email@example.com:amber/helios.git ../heliosto use stock version.
cd ../helios && npm install && cd ../amber.
git clone firstname.lastname@example.org:amber/amber-contrib-legacy.git ../amber-contrib-legacy.
npm install ../helios ../amber-contrib-legacy <maybe others> --no-save.
grunt devel. Prepares some transient files.
amber serve. Starts the integrated development server.
Now you should be able to start Amber devlopment page at
http://localhost:4000/ and commit changes you do to disk.
If you think Amber is not working as expected, You can start by asking on rocket chat or the Mailinglist. Please make sure that you have first checked the following guides:
If the issue can not be resolved you should file an issue on the respective tracker.
Before reporting an issue, try to reduce the issue to the bare minimum required to reproduce it. This allows us to track down and fix the issue in an easier and faster way.
Additionally, you should give us enough information to reproduce the issue. Therefore, include versions of your OS, Amber, Node.js, Grunt, and possibly used libraries as well as sample code. If you don't list the exact steps required to reproduce the issue we won't be able to fix it.
Afterwards, report the issue on one of the following trackers:
If you want to get started developing Amber itself there are a few links to get you started
If you want to get serious with Amber development you should read the Coding Conventions and check if you have all development dependencies installed (as indicated in README):
The Amber development model currently revolves around Pull Requests
git push <your repo> <your branchname>
If you created your clone according to the "Setting up your Amber clone", you should run
in Amber directory to start building from CLI.