Get Started for FREE
Sign up with Facebook Sign up with X
I don't have a Facebook or a X account
 Your new post is loading...
Your new post is loading...
Scoop.it!
This is the second in a series of three blog posts about Rollup, AdRoll's UI component library. This post covers how we build individual components and the developer tools supporting them. All the shared UI components we use at AdRoll live in a private GitHub repository called Rollup. In the repo, each component has its own directory whose name matches the component’s npm package name. All components, and by extension Rollup npm package names, are prefixed with ar- for AdRoll. 
No comment yet.
Sign up to comment
Scoop.it!
Deploying your Ember application can be tricky, and slow if it is tied into your backend, Feifan Wang talks tools and strategies for lean JavaScript app deployment in the context of Rails and Ember.
Scoop.it!
From
jxnblk
React is incredibly intuitive and flexible to work with, but relying solely on client side rendering leaves a lot to be desired in regards to percieved performance. With a static React site, the page loads just like any other static HTML, and the JavaScript kicks in whenever it’s downloaded. This is extremely helpful for combining documentation with interactive demonstrations, like Colorable or Building SVG Icons with React. Using React with webpack also allows you to consolidate the entire build process in Node and take advantage of anything in the npm ecosystem. Last but not least, React is just fun to use.
Scoop.it!
What’s the difference between Gulp and Grunt? While Gulp is a later entry to the field, it has gained popularity for crisp performance and elegant syntax. Unlike Grunt, which tends to read and write files to disk, Gulp uses a stream (Vinyl) object to pipe method results to following methods, allowing calls to be chained together in a fluent syntax. Grunt is an earlier entry in the client-build-tool space. Grunt modules predefine most everyday tasks like linting, minimizing, and unit testing, and Grunt is widely adopted and downloaded thousands of times each day.
Scoop.it!
As mobile device usage continues to grow, developers need to ensure that their mobile websites are fast and offer a high quality experience for all users. A fast mobile website can be the difference between winning or losing a customer. A few seconds delay in your page load time and you might find that users to your site easily become frustrated and navigate away to another site...or even worse, your competitors site!
Scoop.it!
CRAFT is about software craftsmanship, which tools, methods, practices should be part of the toolbox of a modern developer and company, and it is a compass on new technologies, trends. You can learn from the best speakers and practitioners in our community.
Scoop.it!
Broccoli is the blazingly fast build tool used by Ember.js and Ember CLI. Though as we'll see it has uses in any JavaScript project and maybe beyond that.
Scoop.it!
Notable webpack features include:
Scoop.it!
From
gon
I've been using Grunt and Gulp for some time now. However, I've realized lately that with a simple package.json I can do the same, but more manteinable and with less code. In this post, I'll explain how we can do it!!
Scoop.it!
Make is over 30 years old and a standard tool on unix-ey systems (e.g. Linux and OSX). You probably already have it installed on your machine. While it is ubiquitous for C builds, it is flexible enough that you can use it to automate just about anything build-related. I have been a strong proponent of Grunt for the past few years, but I feel like it is too complicated for what it does. I had found myself fighting with it a bit, especially when I needed to define a complicated sequence of processing steps with intermediate artifacts.
Scoop.it!
As a reduced test case for experimentation, I set up a sample repository. The project uses jQuery, Lo-dash, and Handlebars, along with 50-or-so custom CommonJS modules (bundling to half a megabyte) to give Browserify something to work with. In this repository, our ideal build system will do the following (doubly ideal would be doing these things quickly... we'll get there).
Our build process at Pellucid has a few more requirements than this, but these should cover some of the longest operations, and this sample project should be generic enough to apply to many front-end projects.
Scoop.it!
Under normal circumstances, following the official guide for setting up QUnit would have been enough, but there were a couple of issues we had to overcome:
Scoop.it!
The first step was getting hold of QUnit, a Javascript unit test suite capable of executing our tests; in fact, QUnit is apparently used to unit test not only itself, but also JQueryUI, JQuery and JQuery mobile. So that’s all great and groovy, but requires a manual step of launching the document in a browser in order to execute the javascript. Enter Chutzpah, a command-line javascript test runner. It uses PhantomJS to execute javascript in a headless (read:no window) Webkit browser and also allows us to execute it from the command line.
|
Scoop.it!
Want to learn Webpack or React? Get started for free and build a Kanban board by following the example project. SurviveJS - Webpack and React shows you how to build a simple Kanban application based on these technologies. During the process you will learn to:
Scoop.it!
A lot of developers coming to JavaScript world attracted by React.js are confused with the tooling used to produce modern JavaScript code. Webpack, Babel, ESLint, Mocha, Karma, Grunt... what should I use and which tool is doing what?
Scoop.it!
Burke Holland explains how the WebPack module loader let's you load any asset - CommonJS or AMD, JavaScript or CSS - and how to use it with Visual Studio. WebPack calls itself a “Module Bundler”. We tend to think of modules in terms of JavaScript, but WebPack thinks of them in terms of any assets that you might want to transpile, minify and pipe to the browser. JavaScript, TypeScript, CoffeeScript, CSS, SASS, images – it doesn’t matter to WebPack. But this is not the reason why I love it. The reason why WebPack is my tool of choice, is that it bridges the gap between AMD and CommonJS.
Scoop.it!
Recipes for solving common Webpack problems. The purpose of this cookbook is to guide you into the world of React and Webpack. Both are powerful technologies and when used together, frontend development becomes a joy. The cookbook should have something to offer for all skill levels. If you are interested in just React, skip the Webpack part and vice versa.
Scoop.it!
From
marmelab
Webpack is really a great JavaScript bundler, allowing to turn messy and numerous JavaScript into a single minified and optimized script. Yet, we missed a good getting started tutorial. Here is one...
Scoop.it!
Minifying code is essentially the process of stripping away everything unnecessary: everything is condensed onto a single line, files are concatenated together, variables are renamed to be shorter and so on. There’s two main reasons you might want to do this:
Ionic has no automated process to do this but it’s relatively simple to set up your own process using Gulpand Grunt. A lot of this is based off of this tutorial by Agustin Haller which was tremendously helpful to me. The only problem I had with it though is that it relies on cordova hooks, and if you’re using PhoneGap Build to build your application then you won’t be able to use these.
Scoop.it!
![A Baseline for Front-End [JS] Developers: 2015 | JavaScript for Line of Business Applications | Scoop.it](https://img.scoop.it/W0EYRFAv7qpjXJe8UQbjTDl72eJkfbmt4t8yenImKBVvK0kTmF0xjctABnaLJIm9)
It’s been almost three years since I wrote A Baseline for Front-End Developers, probably my most popular post ever. It’s 2015. I want to write an update, but as I sit down to do just that, I realize a couple of things. One, it’s arguably not fair to call this stuff a “baseline” – if you thought that about the original post, you’ll find it doubly true for this one. One could argue we should consider the good-enough-to-get-a-job skills to be the “baseline.” But there are a whole lot of front-end jobs to choose from, and getting one doesn’t establish much of a baseline.
Scoop.it!
Webpack is an amazing tool. It calls itself a "module bundler" but it is much more than that: it provides an infrastructure for building, transforming, and live updating modules. While its wall of configuration options may not be your style, this approach works really well for the problem it's solving.
Scoop.it!
I like React. But React can't do everything, and there are things that make no sense to do as a React component, like plain JS functionality. For instance, if you want an image manipulation component, then by all means write it, but you're not going to also include all the code for the under-the-hood image processing library. You want to keep that separate. What's still missing? That post didn't cover everything, and hopefully it left some questions on the table, so let's address those: what's still missing?
Scoop.it!
First, we need to create a package.json file in the root directory of the your project. Next, we will install a few packages that we will use for this project. Run the following command from the same folder that you added the package.json file. So far, we have been working primarily in the command line. It would be nice if we could integrate with our existing Visual Studio experience. Luckily, we can with the new Task Runner Explorer plugin. Once the plugin is installed, open the Task Runner Explorer from the View –> Other Windows –> Task Runner Explorer menu. This window will show you all the tasks in the gulp file and allow you to bind those tasks to certain Visual Studio events. This way, we don’t need to remember to run the gulp tasks from the command line. The IDE can handle it for us.
Scoop.it!
Exploring continuous integration and scalable hosting for Meteor projects. I’m going to focus on one setup that has worked well for projects I’ve worked on and that I know other production Meteor apps are using. The setup described here uses Modulus, Compose, and Codeship. Leveraging these services has the advantage of keeping deployment and hosting simple, so developers can focus on building their app and spend less time on server configuration and ops work.
Scoop.it!
ReactJS uses a special syntax called JSX, not the normal JS one. Usually, when you want to work with ReactJS JSX files, you need to transform it to a normal JS file and then operate on that file. However, with the help of Reactify, a transform for Browserify, you won’t need to compile jsx to js files anymore, just use it directly from your code.
|
