JavaScript for Line of Business Applications

All Videos of JSConf EU 2014

Node.js is getting more and more mature, no doubt - despite this, not a lot of security guidelines are out there.

In this post I will share some points you should keep in mind when it comes to Node.js security.

Contents:

* No eval, or friends
* Strict mode, please
* Static code analysis
* Testing
* Say no to sudo node app.js
* Avoid command injection
* Temp files
* Securing your web application
* Tools to use
* Stay updated

We’re going to build a Q&A system from scratch starting off with setting up your project using Yeoman and outlining the structure. Along the way we’ll talk about custom elements, material design, routing, authentication, security rules, and record priority. Users will be able to write questions, answers, and comments. Both questions and answers can be upvoted. Using security rules, we’ll make sure that users can only manage their own content within Firebase.

This is an ambitious blog post with a lot of code. If you find an error or aren’t sure how to continue, leave a comment in the post and I’ll make improvements. Walking through this entire series (in progress) could take an hour or two, but by the end you’ll have a thorough understanding of how to build a basic Polymer app.

Detecting whether or not an element is visible in the viewport is very useful when it comes to triggering animations or events. Before you drop in another jQuery plugin though, have a look at how easy it is to create a Mixin that you can add to any View or Component. Once added, you can simply ask that element if it’s in the viewport using the property the Mixin injects.

Every now and then, you want to let your users quickly search for records that you’ve already loaded into your store. We can easily implement naïve search using Ember’s Array#filter and native String prototype methods, but let’s go a little step further and create a custom computed property macro (CPM) that wraps the search so we can easily drop it into other properties.

This article describes on the following topics.

• What is AngularJS?
• Design Pattern used for AngularJS.
• Two way data binding.
• Routing.
• Sample project and description.

Learn the basics of implementing your own authentication layer using accounts-base and accounts-password with the JavaScript framework Meteor 1.0...

accounts-base and accounts-ui are awesome packages that happen to make a heap of assumptions about how you're going to reason about your user's authentication and session management using a system called Accounts. That's alright though, because accounts-ui isn't necessarily intended to be the de facto way to provide access to the API of Accounts. It's there to get newcomers started, to help more experienced developers quickly prototype their ideas, and probably only occasionally remain a permanent fixture of the UI.

Here's a look at how we can replace the functionality of accounts-ui with custom behaviours and appearances. 

Taunus focuses on delivering a progressively enhanced experience to the end-user, while providing a reasonable development experience as well. Taunus prioritizes content. It uses server-side rendering to get content to your humans as fast as possible, and it uses client-side rendering to improve their experience.

While it focuses on progressive enhancement, usability and performance are both core concerns for Taunus. Incidentally, focusing on progressive enhancement also improves both of these. Usability is improved because the experience is gradually improved, meaning that if somewhere along the line a feature is missing, the component is still expected to work.

Here at Viget, we've become huge fans of React. It gives us greater flexibility by working with a virtual representation of the DOM. When the DOM simply becomes an idea, instead of a requirement, rendering becomes just another implementation detail. This is particularly useful when rendering content server-side, loosely diagrammed below...

Now let's get started.

The Angular team at Google provides two tools for testing Angular applications: Karma, a test runner for unit testing, and Protractor, a test framework for writing end-to-end (E2E) tests. In this article, I'm going to be focusing on writing unit tests against Angular applications using Karma. We'll cover some unit-testing basics, Karma details, as well as Angular-specific strategies for writing unit tests that help improve overall developer productivity instead of adding an extra development burden to your application.