Newest grunt init template (updateable by `npm -g install amber-cli`)
actually makes `amber init` generate project that does not use 'virtual'
late-mapped modules for compatibility polyfills and platform selection;
they are all loaded explicitly. It is done is backward-compatible manner
(works with existing 0.19.x amber and 0.9.x amber-dev), but Gruntfile.js
and index.html are a bit changed, Gruntfile.js mentioning polyfills
explicitly and index.html loading app differently as now it returns a
Promise of amber instead of amber itself.
H. Hirzel wrote:
> On 5/4/17, Herby Vojčík<[hidden email]> wrote:
>> H. Hirzel wrote:
>>> Hello Herby
>>> If the README will contain instructions and explanations how to load
>>> polyfills explicitly, I would not mind loading them myself.
>> I don't know if it is needed to invest time to show how to load es5-shim in
>> these days, as nearly every browser now can do ES5 (I am thinking of
>> ditching ES3 completely and rely on ES5 features like strict mode and
>> different .apply semantic, checking their availability at the start and
>> throw), and I plan to leave ES2015 (Promise) shim included by default anyway
>> in amber init, so it will be loaded in index.html (just more explicitly).
>> Would that be enough?
> This seems to be fine for me.
> Or is someone still running on ES3 (if yes, he should
>> probably fix the version on 0.19.x)?
>>> On 5/3/17, Herby Vojčík<[hidden email]> wrote:
>>>> Amber has a few amber-compat-xxx modules which adds some polyfills to it
>>>> automagically, specifically, ES5 for very old and ES2015 (Promise) for
>>>> not-so-old-but-still-old platf
>>>> This automagical inclusion of polyfills is actually done via ugly hack,
>>>> relying on (bug? feature?) of requirejs loader with respect of shim
>>>> config on define-less modules. I'd like to get rid of it, as it is
>>>> holding Amber too strictly bound to single loader and its quirks.
>>>> So I would like to ask,
>>>> 1.) Are your Amber project aiming to run at older platforms, relying on
>>>> amber-compat-xxx (the es2015 one is added by default to any project by
>>>> `amber init`)?
>>>> 2.) If yes, would it be problem for you to actually load your polyfills
>>>> explicitly, before loading amber app itself (Amber was always designed
>>>> to be embeddable into existing environment, not to be at the driver
>>>> seat, so this shouldn't be hard)?
>>>> Thanks, Herby
>>>> You received this message because you are subscribed to the Google
>>>> "amber-lang" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> email to amber-lang+unsubsc
>> [hidden email].
>>>> For more options, visit https://groups.google.com/d/optout.
>> 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/d/optout.
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/d/optout.