DOCSLIB.ORG

Are Software Dependency Supply Chain Metrics Useful in Predicting Change of Popularity of NPM Packages?

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Are Software Dependency Supply Chain Metrics Useful in Predicting Change of Popularity of NPM Packages? Are Software Dependency Supply Chain Metrics Useful in Predicting Change of Popularity of NPM Packages? Tapajit Dey Audris Mockus University of Tennessee, Knoxville University of Tennessee, Knoxville Knoxville, Tennessee Knoxville, Tennessee [email protected] [email protected] ABSTRACT 1 INTRODUCTION Background: As software development becomes more interdepen- The usefulness and success of a software, as for other products in dent, unique relationships among software packages arise and form the market, is reflected by its usage. A true measure of popularity, complex software ecosystems. Aim: We aim to understand the be- or in other words usage, of a software would be the number of havior of these ecosystems better through the lens of software active users for it. Unless software licenses are sold and carefully supply chains and model how the effects of software dependency tracked, the number of active users is virtually impossible to mea- network affect the change in downloads of Javascript packages. sure directly and accurately. The number of downloads is, perhaps, Method: We analyzed 12,999 popular packages in NPM, between the closest approximation for the popularity of a software. NPM 01-December-2017 and 15-March-2018, using Linear Regression (node package manager), which is package manager for JavaScript and Random Forest models and examined the effects of predictors packages, does track the number of downloads for the packages representing different aspects of the software dependency supply and makes the data publicly available, unlike most other package chain on changes in numbers of downloads for a package. Result: managers. Preliminary results suggest that the count and downloads of up- Like most software packages, the JavaScript packages distributed stream and downstream runtime dependencies have a strong effect by NPM have a dependency structure, i.e. one package may have on the change in downloads, with packages having fewer, more other packages as runtime and/or development dependencies (other popular packages as dependencies (upstream or downstream) likely types of dependencies also exist). This dependency network influ- to see an increase in downloads. This suggests that in order to ences the number of downloads of the individual packages, be- interpret the number of downloads for a package properly, it is cause when one package is installed by a user, all of its dependen- necessary to take into account the peculiarities of the supply chain cies are also downloaded and installed automatically (unless they (both upstream and downstream) of that package. Conclusion: Fu- are cached). The number of JavaScript packages on NPM exceeds ture work is needed to identify the effects of added, deleted, and 600K, therefore analyzing the complete dependency network for unchanged dependencies for different types of packages, e.g. build the whole NPM ecosystem is a challenge. The dependencies listed tools, test tools. for a package are direct dependencies, however, those dependencies might have their own dependencies. This complex interconnection CCS CONCEPTS forms a dependency network that can be considered a software · Computing methodologies → Classification and regression trees; supply chain, with the entire set of recursive dependencies of pack- Bayesian network models; Learning linear models; · Software and age being upstream from it, and the packages that are recursively its engineering → Open source model; dependent on it being downstream. In a nutshell we’d like to know if the supply chain has effect on KEYWORDS downloads: RQ: Do the number and downloads of upstream and down- Software Supply Chain, Open Source, Software Popularity, NPM stream dependencies help predict the downloads for popu- Packages, Software Dependency lar JavaScript packages in NPM? ACM Reference Format: We collected data from npms.io and obtained daily, weekly, Tapajit Dey and Audris Mockus. 2018. Are Software Dependency Supply monthly, and yearly download numbers for all NPM packages. Chain Metrics Useful in Predicting Change of Popularity of NPM Packages? . We focus on predicting monthly downloads, because the daily In The 14th International Conference on Predictive Models and Data Analytics in Software Engineering (PROMISE’18), October 10, 2018, Oulu, Finland. ACM, and weekly downloads for most packages exhibit large variations, New York, NY, USA, 4 pages. https://doi.org/10.1145/3273934.3273942 which, presumably, are random in nature, and we do not have suffi- cient history to predict yearly downloads for most packages. We Permission to make digital or hard copies of all or part of this work for personal or collected snapshots of the statistics on all packages roughly every classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation 2 weeks between 01-December-2017 and 15-March-2018, and used on the first page. Copyrights for components of this work owned by others than ACM the data from a snapshot to predict the number of downloads for the must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, packages over the next month. To ensure as little overlap as possible, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]. we did not use the data from a snapshot to predict the number of PROMISE’18, October 10, 2018, Oulu, Finland downloads in the next snapshot, which is 2 weeks apart, but looked © 2018 Association for Computing Machinery. at the one after that, which is roughly 1 month apart. Also, since the ACM ISBN 978-1-4503-6593-2/18/10...$15.00 https://doi.org/10.1145/3273934.3273942 actual number of downloads varies drastically among packages, we PROMISE’18, October 10, 2018, Oulu, Finland Tapajit Dey and Audris Mockus use the logarithm of the ratio of downloads in next month and the packages in NPM meet our criteria across all the snapshots. We used downloads of the previous month as our response variable. To focus the API to collect data on all NPM packages twice a month roughly on the effect of the supply chain aspects we consider only packages 2 weeks apart, once in the beginning of a month and once in the with at least one upstream and one downstream dependency. middle, between 01-December-2017 and 15-March-2018, resulting To answer the RQ we used both linear regression and random in 8 different snapshots. The data collection process takes around forest models. Our preliminary findings suggest that both the num- two days, so the data on all packages are not from the same date, ber and the popularity (measured by the number of downloads) of however, we expect the variance to have been evened out across the dependencies are some of the most important predictors for the all snapshots. Since we are using the data for predicting the ratio change in downloads for NPM packages. These models can help in- of downloads between the current and the next month, we had 6 terpret the download counts and reasons that affect the usage of the usable snapshots (because for the last two we did not have download package. Our findings also suggest that the download number can counts in the next month). be affected (or manipulated) through dependencies and frequent The data collected from npms.io has information on the GitHub updates (probably leading to cache misses). repository of the project, e.g. the number of issues, number of In Section 2, we present the related work in this field. In Section 3, weekly, monthly, quarterly, half-yearly, and yearly commits, the we describe the data. The data analysis and modeling approaches list of contributors and the number of commits by each contributor, used for the study, and the results of the analysis are described in as well as the number of forks and stars. The metadata information Section 4. In Section 5, the implications of the result are presented consists of the list of runtime and development dependencies, the and the ideas for future work are discussed. monthly, quarterly, half-yearly, yearly, and total number of releases 2 RELATED WORK for the project, the name and email of the author and the pub- The term łsoftware supply chainž has been used in 1995 [8]. The lisher, the README text, the list of maintainers and contributors concept has since been used for addressing economic and manage- (as listed in NPM), and the number of daily,weekly, monthly, quar- ment issues in software engineering [6], for facilitating the Software terly, half-yearly, and yearly downloads. We used the number of Factory development environment introduced by Microsoft [7] and these quantities (except the README file) as the variables used for elsewhere. The primary use of software supply chain has been for our analysis. The data also has information about some evaluation identifying and managing risks related to the software development metrics calculated by the npms.io website, which we did not use for process [4, 9]. In this study, we are trying to use the dependency our analysis. For the number of releases and commits, we only used network (the supply chain) for understanding and predicting the the monthly and yearly numbers, because a quick PCA (Principle change of popularity of NPM packages. Component Analysis) suggested that most of the variance (∼80%) The topic of software popularity hasn’t seen much attention, in all the commit and release variables are explained by these two possibly due to the lack of reliable popularity measures. Stars for components. GitHub projects were used to identify the factors impacting popular- As mentioned earlier, the response variable for our study is the ity of GitHub projects [3]. The relationship between popularity of logarithm of the ratio of downloads in next month and the down- mobile apps and their code repository was studied in, e.g.
Load more

Recommended publications
  • Asp Net Jquery Ajax Json Example Wersja
    Asp Net Jquery Ajax Json Example Conquering and exculpatory Thorsten wited clumsily and prickle his heed unforcedly and soothingly. Unanswered and numinous Graig never conscripts observably when Bela shoals his luffas. Oligarchic and ben Ashton held so rifely that Simon sticky his bajada. Dbcontect classes to help, i am glad you will send ajax call will execute and the feedback. Scheduled tasks in asp jquery example will help make them together with an array of products table that will decrease automatically. Provides the asp net jquery json helper method, what the about. Via json format in asp net example given by microsoft json request is given by default name to your network have your data has a formatted result. Comment is shown the asp ajax json request to understand concept is the project, the article we click on the product details. Loads data types, ajax example is, the other articles. Into our method in asp net example we can get request and suggestions will not the future of response, for this by both the _layout. We should then the asp net ajax methods of errors potentially introduced by using chart with razor page without updating the class as an array of the div tag. Developer will call with jquery ajax json or with my things, then passes the database and the body. Message using and the example is the client side method can be the console. Year passed to use jquery json data you know what follows is providing different types in the year. Installing a controller folder and a button to products model, simple example below is, and then the _layout.
    [Show full text]
  • Front-End Development with ASP.NET Core, Angular, And
    Table of Contents COVER TITLE PAGE FOREWORD INTRODUCTION WHY WEB DEVELOPMENT REQUIRES POLYGLOT DEVELOPERS WHO THIS BOOK IS FOR WHAT THIS BOOK COVERS HOW THIS BOOK IS STRUCTURED WHAT YOU NEED TO USE THIS BOOK CONVENTIONS SOURCE CODE ERRATA 1 What’s New in ASP.NET Core MVC GETTING THE NAMES RIGHT A BRIEF HISTORY OF THE MICROSOFT .NET WEB STACK .NET CORE INTRODUCING ASP.NET CORE NEW FUNDAMENTAL FEATURES OF ASP.NET CORE AN OVERVIEW OF SOME ASP.NET CORE MIDDLEWARE ASP.NET CORE MVC SUMMARY 2 The Front‐End Developer Toolset ADDITIONAL LANGUAGES YOU HAVE TO KNOW JAVASCRIPT FRAMEWORKS CSS FRAMEWORKS PACKAGE MANAGERS TASK RUNNERS SUMMARY 3 Angular in a Nutshell ANGULAR CONCEPTS THE LANGUAGE OF ANGULAR SETTING UP AN ANGULAR PROJECT THE STRUCTURE OF AN ANGULAR APP DATA BINDING DIRECTIVES SERVICES AND DEPENDECY INJECTION MULTIPLE COMPONENTS INPUT AND OUTPUT PROPERTIES TALKING TO THE BACK END USING ANGULAR WITH ASP.NET MVC VISUAL STUDIO 2017 SUPPORT FOR ANGULAR SUMMARY 4 Bootstrap in a Nutshell INTRODUCTION TO BOOTSTRAP BOOTSTRAP STYLES COMPONENTS JAVASCRIPT CUSTOMIZING BOOTSTRAP WITH LESS BOOTSTRAP SUPPORT IN VISUAL STUDIO 2017 AND ASP.NET CORE SUMMARY 5 Managing Dependencies with NuGet and Bower GENERAL CONCEPTS NUGET NPM (NODE.JS PACKAGE MANAGER) BOWER SUMMARY 6 Building Your Application with Gulp and webpack WHAT FRONT‐END BUILD SYSTEMS ARE FOR A DEEPER LOOK AT GULP INTRODUCTION TO WEBPACK VISUAL STUDIO 2017 AND BUILD SYSTEMS SUMMARY 7 Deploying ASP.NET Core THE NEW HOSTING MODEL OF ASP.NET CORE INSTALLING ON INTERNET INFORMATION SERVICES ON PREMISE
    [Show full text]
  • Reasonml Install Guide Fall 2019
    CS17 Integrated Introduction to Computer Science Hughes ReasonML Install Guide Fall 2019 Contents 1 Install Guide (Windows) 1 1.1 Installing Node . .1 1.2 WSL.............................................1 1.3 Configuring Visual Studio Code . .2 2 Install Guide (Mac OSX) 2 2.1 Installing Visual Studio Code . .2 2.2 Installing Various XCode Tools (NVM, Node) . .2 2.3 Configuring Visual Studio Code . .5 3 Using ReasonML 5 3.1 Configuring Your Project . .5 3.2 Compiling ReasonML . .5 3.3 Running ReasonML . .5 4 Reason Tools (Browser) 6 1 Install Guide (Windows) 1.1 Installing Node Click here to install Node. 1.2 WSL Follow this guide to install Windows Subsystem for Linux (WSL). Select the Linux Distribution choice Ubuntu, which has an orange icon. Open the "Command Prompt" on your machine and type the following command. This can take a long time to install fully. Let it sit for some time, even if it appears as if it’s not doing anything. Feel free to move on to other steps while it loads. npm install - g ocaml - reason - wsl CS17 ReasonML Install Guide Fall 2019 Inside of Visual Studio Code go to Settings > User Settings. In the upper right-hand corner, click on the icon that looks like a file with an arrow wrapped around it. A window should open up with a file in it. Copy and paste the following lines into the file in between the curly braces and save the file. "reason.path.bsb":"bash - ic bsb", "reason.path.ocamlfind":"bash - ic ocamlfind", "reason.path.ocamlmerlin":"bash - ic ocamlmerlin", "reason.path.opam":"bash - ic opam", "reason.path.rebuild":"bash - ic rebuild", "reason.path.refmt":"bash - ic refmt", "reason.path.refmterr":"bash - ic refmterr", "reason.path.rtop":"bash - ic rtop", "editor.formatOnSave": true, "reason.diagnostics.tools":["merlin","bsb"], "terminal.integrated.shell.windows":"C:\\\\WINDOWS\\\\System32\\\\bash.exe" After the initial install command has terminated, you can now open WSL (Ubuntu).
    [Show full text]
  • Iroha Handbook: Installation, Getting Started, API, Guides, and Troubleshooting
    Iroha handbook: installation, getting started, API, guides, and troubleshooting Hyperledger Iroha community Aug 24, 2021 TABLE OF CONTENTS 1 Overview of Iroha 3 1.1 What are the key features of Iroha?...................................3 1.2 Where can Iroha be used?........................................3 1.3 How is it different from Bitcoin or Ethereum?..............................3 1.4 How is it different from the rest of Hyperledger frameworks or other permissioned blockchains?...4 1.5 How to create applications around Iroha?................................4 2 Concepts and Architecture 5 2.1 Core concepts..............................................5 2.2 What’s inside Iroha?........................................... 13 3 Quick Start Guide 17 3.1 Prerequisites............................................... 17 3.2 Starting Iroha Node........................................... 17 3.3 Try other guides............................................. 19 4 Integrated Projects 29 4.1 Hyperledger Ursa............................................. 29 4.2 Hyperledger Explorer.......................................... 29 4.3 Hyperledger Burrow........................................... 30 5 Building Iroha 37 5.1 Prerequisites............................................... 37 5.2 Installing dependencies with Vcpkg Dependency Manager....................... 39 5.3 Build Process............................................... 40 6 Configure 45 6.1 Configure TLS for client-peer communication (torii).......................... 45 6.2 Deployment-specific
    [Show full text]
  • Manual De Iroha: Instalaci´On,Inicio, API, Gu´Iasy Resoluci´Onde Problemas Выпуск
    Manual de Iroha: instalaci´on,inicio, API, gu´ıasy resoluci´onde problemas Выпуск Comunidad Iroha Hyperledger янв. 26, 2021 Содержание 1 Overview of Iroha 3 1.1 What are the key features of Iroha?................................3 1.2 Where can Iroha be used?......................................3 1.3 How is it different from Bitcoin or Ethereum?..........................3 1.4 How is it different from the rest of Hyperledger frameworks or other permissioned blockchains?4 1.5 How to create applications around Iroha?.............................4 2 С чего начать 5 2.1 Prerequisites.............................................5 2.2 Starting Iroha Node.........................................5 2.3 Try other guides...........................................7 3 Use Case Scenarios 9 3.1 Certificates in Education, Healthcare...............................9 3.2 Cross-Border Asset Transfers.................................... 10 3.3 Financial Applications........................................ 10 3.4 Identity Management........................................ 11 3.5 Supply Chain............................................. 11 3.6 Fund Management.......................................... 12 3.7 Related Research........................................... 12 4 Ключевые концепции 13 4.1 Sections................................................ 13 5 Guides and how-tos 23 5.1 Building Iroha............................................ 23 5.2 Конфигурация........................................... 29 5.3 Deploying Iroha..........................................
    [Show full text]
  • Declare Module Typescript Library
    Declare Module Typescript Library Mahmud quintuplicate fantastically as untenantable Glynn grabbles her jays clot tribally. Measlier and noisier Matthias always scunges enlargedly and tessellating his mitzvahs. Undebauched Gunter enisled: he fledging his padauks philosophically and yore. Roughly speaking, how exactly do we make use of these declaration files in our code base? Not every component fully supports any component type you pass in. The compiler will accept JSX. Component Library is like any other NPM Module. Sometimes, I am exporting it to maintain symmetry with the other files. The types here are fine but they do not truly convey the meaning or intent of the code. Passing CLI arguments via shebang is allowed on Mac but not Linux. But they work differently. Software engineer taught me that a Startup product grows and develops every day. In this article, we are going to learn the structure of the Type Declaration files and their use cases. Mozilla and individual contributors. Now, this means something is wrong with the way PHPStorm interprets tsconfig. Typescript will then also export type definitions together with the compiled javascript code so the package can be used with both Typescript and Javascript. Either choice will solve your error. Dan is a big geek who likes making stuff with computers! Senior Front End Engineer at Modus Create. An introduction to TypeScript's module system techscouting. Plus, this should be true. How do I use it? Now that we have everything set up, etc. Once you have the clone URL, the Redux pattern is a radical departure from the style of programming we are used to.
    [Show full text]
  • A Package Manager for Curry
    A Package Manager for Curry Jonas Oberschweiber Master-Thesis eingereicht im September 2016 Christian-Albrechts-Universität zu Kiel Programmiersprachen und Übersetzerkonstruktion Betreut durch: Prof. Dr. Michael Hanus und M.Sc. Björn Peemöller Eidesstattliche Erklärung Hiermit erkläre ich an Eides statt, dass ich die vorliegende Arbeit selbstständig ver- fasst und keine anderen als die angegebenen Quellen und Hilfsmittel verwendet habe. Kiel, Contents 1 Introduction 1 2 The Curry Programming Language 3 2.1 Curry’s Logic Features 3 2.2 Abstract Curry 5 2.3 The Compiler Ecosystem 6 3 Package Management Systems 9 3.1 Semantic Versioning 10 3.2 Dependency Management 12 3.3 Ruby’s Gems and Bundler 16 3.4 JavaScript’s npm 19 3.5 Haskell’s Cabal 21 4 A Package Manager for Curry 25 4.1 The Command Line Interface 26 4.2 What’s in a Package? 29 4.3 Finding Packages 35 4.4 Installing Packages 37 4.5 Resolving Dependencies 38 vi A Package Manager for Curry 4.6 Interacting with the Compiler 43 4.7 Enforcing Semantic Versioning 46 5 Implementation 51 5.1 The Main Module 52 5.2 Packages and Dependencies 56 5.3 Dependency Resolution 58 5.4 Comparing APIs 71 5.5 Comparing Program Behavior 73 6 Evaluation 85 6.1 Comparing Package Versions 85 6.2 A Sample Dependency Resolution 88 6.3 Performance of the Resolution Algorithm 90 6.4 Performance of API and Behavior Comparison 96 7 Summary & Future Work 99 A Total Order on Versions 105 B A Few Curry Packages 109 C Raw Performance Figures 117 D User’s Manual 121 1 Introduction Modern software systems typically rely on many external libraries, reusing func- tionality that can be shared between programs instead of reimplementing it for each new project.
    [Show full text]
  • Investigating the Reproducbility of NPM Packages
    Investigating the Reproducbility of NPM packages Pronnoy Goswami Thesis submitted to the Faculty of the Virginia Polytechnic Institute and State University in partial fulfillment of the requirements for the degree of Master of Science in Computer Engineering Haibo Zeng, Chair Na Meng Paul E. Plassmann May 6, 2020 Blacksburg, Virginia Keywords: Empirical, JavaScript, NPM packages, Reproducibility, Software Security, Software Engineering Copyright 2020, Pronnoy Goswami Investigating the Reproducbility of NPM packages Pronnoy Goswami (ABSTRACT) The meteoric increase in the popularity of JavaScript and a large developer community has led to the emergence of a large ecosystem of third-party packages available via the Node Package Manager (NPM) repository which contains over one million published packages and witnesses a billion daily downloads. Most of the developers download these pre-compiled published packages from the NPM repository instead of building these packages from the available source code. Unfortunately, recent articles have revealed repackaging attacks to the NPM packages. To achieve such attacks the attackers primarily follow three steps – (1) download the source code of a highly depended upon NPM package, (2) inject mali- cious code, and (3) then publish the modified packages as either misnamed package (i.e., typo-squatting attack) or as the official package on the NPM repository using compromised maintainer credentials. These attacks highlight the need to verify the reproducibility of NPM packages. Reproducible Build is a concept that allows the verification of build artifacts for pre-compiled packages by re-building the packages using the same build environment config- uration documented by the package maintainers. This motivates us to conduct an empirical study (1) to examine the reproducibility of NPM packages, (2) to assess the influence of any non-reproducible packages, and (3) to explore the reasons for non-reproducibility.
    [Show full text]
  • Jhipster.NET Documentation!
    JHipster.NET Release 3.1.1 Jul 28, 2021 Introduction 1 Big Picture 3 2 Getting Started 5 2.1 Prerequisites...............................................5 2.2 Generate your first application......................................5 3 Azure 7 3.1 Deploy using Terraform.........................................7 4 Code Analysis 9 4.1 Running SonarQube by script......................................9 4.2 Running SonarQube manually......................................9 5 CQRS 11 5.1 Introduction............................................... 11 5.2 Create your own Queries or Commands................................. 11 6 Cypress 13 6.1 Introduction............................................... 13 6.2 Pre-requisites............................................... 13 6.3 How to use it............................................... 13 7 Database 15 7.1 Using database migrations........................................ 15 8 Dependencies Management 17 8.1 Nuget Management........................................... 17 8.2 Caution.................................................. 17 9 DTOs 19 9.1 Using DTOs............................................... 19 10 Entities auditing 21 10.1 Audit properties............................................. 21 10.2 Audit of generated Entities........................................ 21 10.3 Automatically set properties audit.................................... 22 11 Fronts 23 i 11.1 Angular.................................................. 23 11.2 React................................................... 23 11.3 Vue.js..................................................
    [Show full text]
  • Ajax Form Asp Net Core
    Ajax Form Asp Net Core Indecent Cammy lugging that afterthoughts rewrote contractedly and replevy irascibly. Is Marty trickier or demagogic when henpecks some aftershock assails everyplace? Idlest or indifferent, Randal never commixes any subductions! That script tag and ajax form asp core and handle it so append the form submit a coffee here you can build on Following ajax form data to take input fields. The form returns are using jquery in asp core, trademarks of forms and whatnot in asp core. Save me from asp core razor ajax form element corelated with asp iisserver returns. Now save the database table using this to. Net core asp core mvc what is! NET without additional programming effort. Gets or register to. Ajax helper ajax to. Route is ajax form was already subscribed. Download sample applications like jquery? In news post they saw how drug use ASP. Index action that i am happy that cover common question was very important? Net core asp tutorial showing redundant validation to form for forms using ajax query to add validation using a guide. The ajax forms, we want it? When a user creates a new goat an ID is generated automatically. Net core asp iisserver returns and form requests? Introduction to Razor Pages in ASP. Stop relying on asp core. Gets or views in ajax forms with an attacker entered by adding blocks of asp core web application more have any error. From ajax form element with asp core web application we receive no comments about this property such as part of steps to get updated to register a sample asp.
    [Show full text]
  • Modern Web Development
    Arjen de Blok Senior Technical Consultant bij ICT Groep (www.ict.eu) sinds 1995 Programmeren sinds 1990 Technologiën Visual C++ met Microsoft Foundation Classes .NET WinForms & WPF Silverlight ASP.NET WebForms, MVC, Web API Microsoft SharePoint KnockoutJS, PagerJS, TypeScript, SASS AngularJS, TypeScript, SASS Aurelia, WebPack, TypeScript, SASS Links Github: https://github.com/arjendeblok Agenda 1. Basics for every web developer 2. Road to the Client Side 3. Putting it all together 4. Aurelia 5. Demo RecipeWeb Pauze 6. Back to the Server Side with ASP.NET Core 7. Testing your Aurelia App Part 1 Basics for every web developer Web Development Everywhere For the browser Web Sites Web Apps For mobile Apache Cordova For desktop Windows 10 UWP Electron For smart watch Samsung Tizen HTML 5 Previous version 4.01 released in 1999! Draft since 2007 Finalized in 2014 Internet Explorer support 9+ New document type Consists of many features Check for browser support! http://html5test.com/ Works in conjuction with CSS 3 and JavaScript Semantic HTML HTML5 tags <header>, <footer> <article> <nav> <aside> List tags <ul>, <ol>, <li> Use them in CSS Less class selectors HTML 5 Additional Features New Input Types Number, Date, Time, Range Graphics Vector - SVG Bitmap - Canvas 3D - WebGL Video & Audio Native Tag Streaming Storage Web Sockets CSS 3 Extension of CSS 2 Additional CSS Selectors like attribute and child selectors. Border styles like border-radius and box-shadow. Text effects like text-shadow 2D/3D Transformations Animations Transitions JavaScript Specification: ECMAScript Version ES5 supported on all browsers ECMAScript 2015 or ES6 partially supported on Edge, Chrome, FireFox ECMAScript 2016 or ES7 partially supported on Edge, Chrome, FireFox Transpilers for compiling ES 2015/2016 to ES5 Babel TypeScript 2.1 Traceur https://kangax.github.io/compat-table/es6/ Important: ES6 Promise pattern.
    [Show full text]
  • Patterns of Modern Web Applications with Javascript
    Patterns of Modern Web Applications with Javascript Ken Chau This book is for sale at http://leanpub.com/patterns-of-modern-web-applications This version was published on 2015-07-10 This is a Leanpub book. Leanpub empowers authors and publishers with the Lean Publishing process. Lean Publishing is the act of publishing an in-progress ebook using lightweight tools and many iterations to get reader feedback, pivot until you have the right book and build traction once you do. ©2015 Ken Chau Contents Introduction ............................................ 1 Who This Book is For ...................................... 1 Overview ............................................ 1 Acknowledgements ....................................... 2 Help and Support ........................................ 2 Part 1. Javascript Environments and Modularity .................. 3 Chapter One: Javascript Runtime Environments ....................... 4 Versions of Javascript ...................................... 4 Chapter Two: Patterns of Modularity .............................. 11 Introduction Who This Book is For Web development technology has shifted from server to client. This allowed for highly interactive applications to be developed in the style of Single Page Applications (SPA). Traditional server- rendered pages are becoming more and more extinct as Web browsers and hardware are getting faster and faster. As developers develop these complex applications, new patterns are emerging that would solve some problems presented by the “traditional” SPA’s. I have written this book for developers like me. I’m assuming that you come from a background of Web development. This should probably not be the book you use to start learning Web development. I hope to share lessons learned from building large and complex Web applications. This book captures the common design and architecture pattern found in modern Web development today. In this book, I am focusing on the front-end Web development stack written in Javascript.
    [Show full text]