I am NOT much used to handlebars, can i completely skip handlebars and use angular. I see couple of libraries of angular in mtr which one to use, please suggest? Also provide any feedback if there will be problems in my app if i completely go the angular way in meteor.
I don't know angular very well, but I've already tried using meteor with KnockoutJS. My first impressions are that this should work fine. However, one important thing to keep in mind is that those frameworks use totally different dependency tracking system and in some cases it can be tricky to synchronize them with meteor, e.g. with reactive data sources like Collection.
Loneleeandroo has a great package on GitHub called ngMeteor to use for integrating the two frameworks together. It's really, really slick. Here's a link for you: https://github.com/loneleeandroo/ngMeteor/
Hope this helps!
The angular-meteor project has the most traction on github, is actively maintained, and has a well done tutorial.
http://angular-meteor.com/
tutorial
http://angular-meteor.com/tutorial
github
https://github.com/Urigo/angular-meteor
Related
I chanced on Piral Framework for implementing micro-frontends and I wanted to implement it in my project.
However, my application comes as a Blazor wasm project and my aim is to use this current project as my app shell.
Is there any example on how I could implement that?
I can't really find my way around the documentation too.
Kindly note that I am a beginner. Thanks in advance.
For the app shell you cannot use Blazor.WASM. You can, however, make your app shell really lightweight (i.e., don't put almost anything in there) and have all the necessary layout parts defined in Blazor.
The idea boils down to the sample given at:
https://github.com/piral-samples/piral-distributed-layout
Now instead of having pilet(s) in React / Angular / ... you use Blazor.
For Blazor pilets (and extensions using Blazor) you can check out the documentation at the README of Piral.Blazor:
https://github.com/smapiot/Piral.Blazor/
Make sure to follow the instructions closely and use the right branch (named after the version of Blazor you are targeting).
After searching around on how to actually implement the concept of micro-frontends using Blazor WASM as my app shell, I still didn't find any solution which helped me. So I came up with a custom solution which I wrote about in a blog.
Basically, the solution makes use of the JS interop of Blazor as a medium of communicating between the other JS frameworks or libraries.
Kindly have a read: https://dev.to/xanderselorm/introduction-to-micro-frontends-using-net-blazor-wasm-part-1-lc9
Next.JS simplifies lots of stuff for creating the Web App. But the modelling data and the API and the data communication between the Server and the Client stays pretty much the same as in other React.JS apps.
A lot of code needed to be written to make it possible. I wonder if there's some approach or extension for Next.JS that would make it easier? Something like meteor or like that?
Realise this is an old question, but take a look at Blitz JS - this wasn't around at the time the question was asked, but has been one of 2020's top projects on Github. It's built on Next.js and is designed to abstract away the complexities of an API. It's trying to be the Rails of the JS world.
We are building a marketplace using angular and we want to integrate Adyen payments. Googling for 'Adyen angular' or 'Adyen SPA' or even 'Adyen react' doesn't bring any useful results. NO results whatsoever.
Therefore I am left wondering, why the whole world (including Adyen docs) is not talking about integrating Adyen into a SPA.
It doesn't seem to be more vulnerable to network security attacks to me. At least I can't think of any reasons for that.
Please help me to understand, what I am missing out.
As madesch mentioned, integrating in a SPA shouldn't be too far from other kinds of integrations. Are you having issues with something in particular?
Here can see an integration with Vue, one with React and even one with React Hooks.
The card fields are not being loaded because I'm not using a real originKey, but it should give you an idea about how to do the integration.
I hope it helps!
It seems that I overestimated Adyen popularity and in reality, the truth is that it is just not popular enough to have gotten attention from SPA community. :(
it seems like originKey is deprecated, the current recommendation is to use Web DropIn. But this requires using a server component, as you don't want to expose your API key, right?
So if you don't want to use a deprecated API, you must always add a server component to your stack. A pure SPA does not seem to be possible using current APIs, it seems.
There are now few options available:
Angular support
Vue support
React support
All examples are based on the Web Drop-in approach which renders a checkout component with the supported/requested payment methods.
A basic explanation of the workflow is provided here.
Just started to discover meteor. created app with DiscoverMeteor book, but misunderstood many moments. then read Your first meteor application and Your first meteor application books. Realized that Todos example is really too simple to cover many important things. And only after that I found the official guide on Meteor.com! now reading about all these complex (for my opinion) things. and have 2 questions:
What router should I prefer to use? I want to create fast app with lots of data loading from the server. Found information that Iron router is deprecated, and Flow router is recommended nowadays, but also found that flow router can not route on server, only on client. And that exactly client routing is the reason why for example soundcloud is really slow. So that is the question - I know nothing about server/client routing, but want to make right decision for the future project.
What ui-framework to use? I read that blaze is easy to start, but react js is really powerful. So: is Blaze enough for serious project (like a popular blog)? Or do I have to learn react js in order not to rewrite code in the future?
I am working with Meteor 1.3.2.4, which is latest in market and believe, you don't have to do anything out of the box to go with experimental UI-Frameworks and stuff.
Blaze template which is handlebars based implementation is best.
Blaze template is very well glued with Socket.io, futures and DDP implementation for cutting edge implementation for asynchronous and reactive behaviour on UI.
Blaze is really good for cumbersome, heavy data websites as well. If you have any doubt, i can skype and show you what i have implemented in just 2 days on development using everything given by Meteor.
React.js, Koa.js (re-written Express framework), express etc are very good and powerful, but I think implementing it at initial level of your grasp is overkill. Go with Blaze first.
There are hundered sitting and developing Meteor.js just for you to be comfortable. I am not at all biased, I am giving you my open opinion.
I worked with Laravel 5.2, Play framework, MEAN.io, DJango in past, but believe there is nothing like pure Meteor js with there own packages. There are many videos on youtube like Meteor nights and stuff where you can find the developers from all around the world developing huge stuff just using stuff given by Meteor js.
For routing flow-router is good, even iron:router is awesome and easily gettable.
This video can guide you very well.
Flow Router is the recommended router by the official Meteor Guide. It's also the popular choice these days, and for a reason: it's a high quality router implementation.
As for MVC, it's really like choosing a religion. React has a huge community, possibly a bright future, and it's not Meteor-only unlike Blaze. But some folks find Blaze templates nicer than JSX files. I think it's easier to get help on StackOverflow if you pick React, but Blaze might be easier to get started.
Maybe this post helps a bit: How to set up React with Meteor?
Does anyone know if this script will continue to have a future or is it DOA and being replaced by another component? I use its functionality a lot and would like to know if there is a better alternative or what the future holds for it...
To clarify, I'm talking about the async loader features in start.js.
None of the ASP.NET Ajax Library (not to be confused with ASP.NET AJAX) was officially released and development on it ceased before it was complete. You shouldn't use it. I've wrote an article on the subject.
The same team at Microsoft has produced a new script loader, DeferJS, which is the next logical evolution of Sys.require. You can find the latest version of it here: https://github.com/BorisMoore/JsDefer
There's not going to be any further development on sys.require, but the existing scripts and services will not disappear. Microsoft has taken considerable measures to maintain backwards compatibility with its older technologies, so there's no reason to think that what you have working now will suddenly stop working at some point in the near future.
Microsoft seems to be going in the direction of integrating with the open source jQuery library. Here's a blog post about it: http://weblogs.asp.net/scottgu/archive/2008/09/28/jquery-and-microsoft.aspx. jQuery is very powerful and flexible, and has both built in support as well as a plethora of plugins for AJAX.
There's also RequireJS (http://requirejs.org/), which is quite mature, and somewhat easier to use. It's not from Mircosoft, but it may be worth a look.
May be you can try this
it is an extensible resource loader, and it does dependencies tracking.