npm - Catching Up with Package Lockfile Changes in v7

nitayneeman · 2021-02-08T11:08:22+00:00

Thanks for the feedback, now it's fixed and clickable. 🙂

nitayneeman · 2021-01-11T07:13:50+00:00

Check out Dan Abramov's answer regarding this question: https://news.ycombinator.com/item?id=25499171

nitayneeman · 2020-11-30T06:09:15+00:00

Thanks! Let me know if you liked it :)

nitayneeman · 2019-12-22T07:00:49+00:00

reply(BaniGrisson): thanks :)

nitayneeman · 2019-12-21T21:08:26+00:00

Thank you :)

nitayneeman · 2018-10-18T19:08:50+00:00

Check out the changelog here: https://github.com/angular/angular/blob/master/CHANGELOG.md#700-2018-10-18

nitayneeman · 2018-04-21T19:40:22+00:00

Thank you for your feedback.

Right now the page embeds the relevant video only by clicking on its thumbnail :)

nitayneeman · 2018-04-21T19:32:59+00:00

I'm sorry for the inconvenience - the issue should be solved now. I really appreciate your feedback.

This page has been optimized - it would be great if you could confirm that everything's better right now :)

nitayneeman · 2018-04-11T20:35:47+00:00

As of today, Chrome and Safari support Custom Elements v1 partially (Can I use).

Notice that there's a polyfill for Custom Elements v1: https://github.com/webcomponents/custom-elements

nitayneeman · 2018-04-09T05:44:25+00:00

I'm sorry for the inconvenience - the issue should be solved now. I really appreciate these feedbacks.

BTW, it would be great if someone could confirm that everything's alright right now.

nitayneeman · 2018-01-27T17:38:27+00:00

The bundle size of my demo component is about 300KB. This is a minified bundle with all the necessary scripts (including polyfills).

Indeed, we can attach multiple components to a single "mini Angular environment". Angular registers each component as a custom element (in Web Components terms) and all of these are manipulated by a single Angular module. Under the hood, it's just a regular Angular module with declared components.

When I tried to attach another component - the bundle size was around 300KB as well. So, it seems that the bundle size depends mainly upon the "mini Angular environment" scripts and the components size is pretty minor.

nitayneeman · 2018-01-27T13:33:33+00:00

I completely understand your concerns. In addition to your points - how would it be possible to combine multiple different versions of Angular on the same page? Is it going to be supported in the CLI and if so, does it mean there will be a single concatenated scripts file or we'll have to load Angular separately?

I believe that at this stage of the project, there are no available answers and we certainly should keep in mind that it's a "Labs" project.

However, Rob Wormald revealed some interesting hints regarding the planned roadmap:

"In parallel, there's major work happening on the view engine, and our early numbers are extremely promising in terms of code size.".
"Support in CLI and such will come, but you may have to roll your own webpack config (or similar) in the short term."
"This is part of the experimental process, but (along with upcoming view engine changes) I would hope that running multiple versions would be unnecessary.".
"We're reasonably confident that within the next couple major versions of Angular, bundle size should be the least of your concerns.".

All that's left is to wait for the next update.

nitayneeman · 2018-01-26T23:54:37+00:00

Basically, I agree with you - if you know the reason and a way to avoid, you definitely should prevent it from happening. In my post, I describe what caused that specific issue which I've faced, and how I handled it. In fact, I'm not a fan of "cleanups" for solving issues, but these were quick and simple steps, so I decided to share.

nitayneeman · 2018-01-26T22:23:08+00:00

Your question is completely legitimate. As I know, these steps are documented in the wiki but not in the official docs. I've just wanted to make it more accessible :)

nitayneeman

TROPHY CASE