Being completely new to the Node world, I only just discovered about the npm start command. It seems like a much better way to launch amber, but the package.json doesn't include a start: key. I was wondering if there was a reason for that?
-- Cheers Andy You received this message because you are subscribed to the Google Groups "amber-lang" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/groups/opt_out. |
1. Nobody probably though of it.
2. There are more verbs ahead in amber than just 'start'. So, it will probably stay as planned, to install executable for it (as grunt-cli or express do; a lot of npm project does so in fact). Andy Burnett wrote: > Being completely new to the Node world, I only just discovered about > the npm start command. It seems like a much better way to launch > amber, but the package.json doesn't include a start: key. I was > wondering if there was a reason for that? > > Cheers > Andy > > -- > You received this message because you are subscribed to the Google > Groups "amber-lang" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [hidden email]. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "amber-lang" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/groups/opt_out. |
Unfortunately, I know so little about node/npm, I don't really know if I am asking the right question. However, I did take the start up string from the server file, and stick it in the package.json file - under a "start": key, and I can now fire up amber from any directory just by typing npm start amber which is quite useful :-) I didn't try to include the directory variable, so it appears to default to the amber directory - but I haven't experimented with that yet.
Anyway, the point is that if this doesn't cause problems, it might be worth including in a future package.json file, just to help people get started. Cheers Andy
On Fri, Nov 8, 2013 at 2:07 PM, Herby Vojčík <[hidden email]> wrote: 1. Nobody probably though of it. You received this message because you are subscribed to the Google Groups "amber-lang" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/groups/opt_out. |
Again: why compicate it with "npm start"? You can start amber from anywhere (if you installed it with -g) by just "amber" (you should use proper command, of course, 'amber repl' or 'amber serve').
Herby Andy Burnett wrote: > Unfortunately, I know so little about node/npm, I don't really know if > I am asking the right question. However, I did take the start up > string from the server file, and stick it in the package.json file - > under a "start": key, and I can now fire up amber from any directory > just by typing > > npm start amber > > which is quite useful :-) > > I didn't try to include the directory variable, so it appears to > default to the amber directory - but I haven't experimented with that yet. > > Anyway, the point is that if this doesn't cause problems, it might be > worth including in a future package.json file, just to help people get > started. > > Cheers > Andy > > > On Fri, Nov 8, 2013 at 2:07 PM, Herby Vojčík <[hidden email] > <mailto:herby > > 1. Nobody probably though of it. > 2. There are more verbs ahead in amber than just 'start'. > > So, it will probably stay as planned, to install executable for it > (as grunt-cli or express do; a lot of npm project does so in fact). > > Andy Burnett wrote: > > Being completely new to the Node world, I only just discovered > about the npm start command. It seems like a much better way > to launch amber, but the package.json doesn't include a start: > key. I was wondering if there was a reason for that? > > Cheers > Andy > > -- > You received this message because you are subscribed to the > Google Groups "amber-lang" group. > To unsubscribe from this group and stop receiving emails from > it, send an email to [hidden email] > <mailto:amber-lang%[hidden email]>. > For more options, visit > https://groups.google.com/__groups/opt_out > <https://groups.google.com/groups/opt_out>. > > > -- > You received this message because you are subscribed to the Google > Groups "amber-lang" group. > To unsubscribe from this group and stop receiving emails from it, > send an email to [hidden email] > <mailto:amber-lang%[hidden email]>. > For more options, visit https://groups.google.com/__groups/opt_out > <https://groups.google.com/groups/opt_out>. > > > -- > You received this message because you are subscribed to the Google > Groups "amber-lang" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [hidden email]. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "amber-lang" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/groups/opt_out. |
Ah, the answer is easy - ignorance :-) On Tue, Nov 12, 2013 at 7:37 AM, Herby Vojčík <[hidden email]> wrote: Again: why compicate it with "npm start"? You can start amber from anywhere (if you installed it with -g) by just "amber" (you should use proper command, of course, 'amber repl' or 'amber serve'). You received this message because you are subscribed to the Google Groups "amber-lang" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/groups/opt_out. |
Free forum by Nabble | Edit this page |