DOCSLIB.ORG

Integrating a Modern Frontend Setup with AEM Natalia Venditto, Netcentric a Modern Frontend Setup

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Integrating a Modern Frontend Setup with AEM Natalia Venditto, Netcentric a Modern Frontend Setup APACHE SLING & FRIENDS TECH MEETUP 10-12 SEPTEMBER 2018 Integrating a Modern Frontend Setup with AEM Natalia Venditto, Netcentric A modern frontend setup 2 How do we understand a modern setup? ▪ A modern setup ▪ ...does not necessarily include the latest tool in the market ▪ …it's standard enough that it can be easily maintained ▪ …does not force everyone in the team to a high knowledge ramp up investment ▪ …it implements industry (current) best practices ▪ ...requires a strategy 3 Defining a frontend strategy! photocredit: @rawpixel / unsplash.com 4 The `What?` and `How?` questions WHAT? HOW do we achieve? questions for your client questions for your team ieve / unsplash.com … browser support, performance reqs, http protocol (ie: http/2), accessibility, analytics, testing strategy, more productivity? photocredit: @kevingr 5 The `Which?` questions Which Build Which AEM Which JS Which CSS Tools/ features? Setup ECMAScript Spec Which Bundlers What version of Frameworks Preprocessor? Task Runners AEM? What new State Manag. (SASS, LESS, Linters/Coverage features? 3rd party/APIS PostCSS) Loaders/Plugins Clientlibs strategy 6 The win/win results matrix increased performance (author + end user experience/ROI, etc) enhanced productivity/flexibility guaranteed innovation/creativity (code quality, (browser feature support, testability, maintenance, accessibility) scalability) 7 Study case: directory structure 8 Directory structure . ~ |-- [PROJECT-ID]-3rd-party/ |-- [PROJECT-ID]-complete-package/ |-- [PROJECT-ID]-components/[PROJECT-ID]-components-package/ |-- src/main/jcr_root/apps/[PROJECT-ID]/ |-- commons/ |-- components/ |-- component1/ |-- component2/ |-- // as many components |-- pages/ |-- [PROJECT-ID]-configuration/ |-- [PROJECT-ID]-demo-content/ .pom.xml 9 Directory structure <?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" |-- components/component1/ jcr:primaryType="cq:ClientLibraryFolder" |-- clientlibs/ categories="[PROJECT-ID.publish.component1 |-- author/ ]" jsProcessor=”[min:gcc;obfuscate=true]” cssProcessor=”[min:gcc]” |-- publish/ /> |-- .content.xml |-- component1.publish.entry.js |-- component1.publish.entry.scss |-- css.txt |-- js.txt |-- .content.xml |-- component1.html 10 Study case: tools and configuration 11 Tools and configuration 12 Tools and configuration File Loaders Plugins Output System ▪ configure webpack to ▪ configure webpack to read ▪ configure webpack to traverse our component files according to output files in designated folders, collect loaders, and perform targets, so that we are able [name-of-component].entry.js additional operations to minify them, [name-of-component].entry.scss (transpilation, tree-shaking aggregate them and files and DCE, etc) compress them (in AEM (webpack allows us to configure with gcc) entry points per path or other params) 13 Setup Tools nvm install --lts cd [PROJECT-ID]-components/[PROJECT-ID]-components-package mkdir frontend cd frontend npm init –y // generates package.json npm install webpack -–save-dev // maintain as dev dependency //successive installations npm install modulename --save || --save-dev 14 Setup Tools test: /\.css$/, Transpiling Transpiling of CSS Browser of ES pre Linting Support (to JS ES5) processed code 15 Setup configuration . ~ |-- [PROJECT-ID]-components/[PROJECT-ID]-components-package/ |-- frontend/ last 2 version |-- .browserslistrc |-- .eslintignore > 1% |-- .eslintcache maintained node versions not dead |-- .eslintrc |-- .stylelintcache |-- .stylintrc |-- .gitignore |-- .npmrc |-- package.json .pom.xml 16 Setup Tools test: /\.css$/, Transpiling Minification Transpiling of CSS Browser Aggregation of ES pre Linting Support of JS and (to JS ES5) processed CSS code 17 Directory structure <?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" |-- components/component1/ jcr:primaryType="cq:ClientLibraryFolder" |-- clientlibs/ categories="[PROJECT-ID.publish.component1 |-- author/ ]" jsProcessor=”[min:gcc;obfuscate=true]” cssProcessor=”min:gcc]” |-- publish/ /> |-- .content.xml |-- component1.publish.entry.js |-- component1.publish.entry.scss |-- css.txt |-- js.txt |-- .content.xml |-- component1.html 18 Setup configuration . ~ |-- [PROJECT-ID]-3rd-party/ |-- [PROJECT-ID]-complete-package/ |-- [PROJECT-ID]-components/[PROJECT-ID]-components-package/ |-- frontend/ |-- build/config/ |-- webpack.config.dev.js |-- webpack.config.prod.js |-- whatever other configs (ie: unit testing, e2e...) |-- package.json |-- [PROJECT-ID]-configuration/ |-- [PROJECT-ID]-demo-content/ .pom.xml 19 Setup configuration ▪ for our frontend code build, we will favor webpack 4 optimized "mode" configuration, over OSGI environment definition, in order to leverage Webpacks caching and performance 20 Setup configuration 21 Setup configuration may need to update this (default) config for SplitChunkPlugin 22 Setup configuration ▪ edit the corresponding POM.xml, to make use of the frontend plugin for maven* -> https://mvnrepository.com/artifact/com.github.eirslett/frontend-mave n-plugin?repo=redhat-ga 23 Maven frontend plugin 24 Syncing with AEM webpack --watch 25 Setup configuration |-- components/component1/ |-- clientlibs/ |-- author/ |-- .content.xml |-- component1.author.entry.js |-- component1.author.scss |-- css.txt |-- js.txt |-- component1_dialog.js |-- publish/ |-- _cq_dialog/ |-- .content.xml |-- component1.html 26 Setup configuration . ~ |-- [PROJECT-ID]-components/[PROJECT-ID]-components-package/ |-- frontend/ |-- .browserslistrc |-- .eslintignore *.bundle.js |-- .eslintcache node_modules |-- .eslintrc *_dialog.js |-- .stylelintcache build/shared/variabl |-- .stylintrc es/*.js |-- .gitignore node/* |-- .npmrc |-- package.json build/config .pom.xml gulpfile.js 27 Study case: shipping the code (to the browser) 28 Loading styles via Content Policies 29 Loading techniques 30 Loading: Templating (Sightly, Handlebars...) |-- components/component1/ |-- clientlibs/ |-- author/ |-- publish/ <!--/* component1.author */--> <sly data-sly-test="${wcmmode.edit}" |-- additional-styles/ data-sly-use.clientLib="${'/libs/granite/sightly/tem plates/clientlib.html'}" |-- .content.xml data-sly-call="${clientLib.all @ categories='[PROJECT-ID].component1.author'}" /> |-- component1.add-styles.entry.js |-- component1.add-styles.scss<!--/* component1.publish */--> <sly |-- css.txt data-sly-use.clientLib="${'/libs/granite/sightly/tem |-- js.txt plates/clientlib.html'}" data-sly-call="${clientLib.all @ categories='[PROJECT-ID].component1.publish'}" /> |-- .content.xml |-- component1.html 31 Script loading attributes <script src="myproject.component1.js" defer></script> <script src="myproject.component1.js" async></script> <script src="myproject.component1.js" preload></script> <script ... 32 Lazy Loading 33 Inline load + Lazy Loading strategy hero area/above the fold lazy loaded chunks (and resources, such as images) 34 Intersection Observers API // test for browser support if (!'IntersectionObserver' in window && !'IntersectionObserverEntry' in window && !'intersectionRatio' in window.IntersectionObserverEntry.prototype) { // load polyfill now } 35 LazyLoading and SEO ▪ SSR (server side rendering techniques) ▪ Content Fragments ▪ Experience Fragments 36 Demo Time (added backup) 37 Loading styles via Content Policies 38 Loading styles via Content Policies 39 Loading styles via Content Policies clientlibs="some.c ategory" 40 Thank you! 41.
Load more

Recommended publications
  • Paul M. Graffam Email: [email protected] ● Website: Paulgraffix.Com ​ ​ ​ ​ ​ ​ ​
    Paul Graffam Resume Paul M. Graffam Email: [email protected] ● Website: paulgraffix.com ​ ​ ​ ​ ​ ​ ​ Professional Profile ● 7+ years of work experience in programming and 4 years in agency. ● Ability to work collaboratively with colleagues across disciplines. Enthusiastic, ​ positive attitude and self-starter. ● Eager to meet challenges and quickly assimilate newest technologies, skills, concepts, and ideas. ● Self-motivated and detail orientated with strong ability to multitask. ● Superior computer skills. Proficiency with many applications as well as hand coding with a variety of IDEs. Highly capable with either PC or Mac. ● Creative troubleshooter/problem-solver who works hard and loves a challenge. ● Bilingual: fluent in both English and Spanish. Skills Front End Back End Other ● XHTML & HTML5 ● PHP ● Windows ​ ​ ​ ● CSS3 & CSS4 (postCSS) ● Python ● Mac ​ ​ ​ ● Javascript (ES5 & ES6) ● Ruby & Rails/ERB ● Linux ​ ​ ​ ● jQuery ● VB/C# .NET ● Adobe CS ​ ​ ​ ● LESS/SASS/Stylus ● SQL/NoSQL (mongoDB) ● Visual Studio ​ ​ ​ ● Grunt/Gulp/Browserify ● XML & XSL ● Sublime Text/Atom ​ ​ ​ ● Webpack ● Apache/Google App Engine ● WebStorm ​ ​ ​ ● React/Angular/Backbone ● Heroku/Firebase/Azure/AWS ● Git/SVN ​ ​ ​ ● Bower/NPM ● Node.js & Express ● SQL Server ​ ​ ​ ● Bootstrap/Foundation ● CMSes (Craft, Contentful, ● Unity3D ​ ​ ​ ● Handlerbars/Moustache Drupal, Sharepoint, Wordpress) ● Bash/SH ​ ​ ● Jade/HAML ● Social APIs ● Premiere/Final Cut ​ ​ ​ ● WebGL/Three.js Pro ​ Work Experience Interactive Developer for Stinkdigital - Dumbo, NY Oct ‘15 – Jul ‘16 ​ ​ ​ ​ ● Immersed into a massive project for Spotify’s Year in Music on the first day, ​ ​ ​ ​ working on both the front and back end. Consisting of a responsive WebGL experience via pixi.js and tied to Spotify’s API, translated into 35 languages all managed by a custom CMS. Received multiple Webbys, FWA and Awwwards winners.
    [Show full text]
  • Webpack Cheatsheet
    12/25/18, 655 PM Page 1 of 1 ! Edit Webpack cheatsheet — Proudly sponsored by — Airbrake.io Full-stack error tracking & analytics for Python developers. Try it Free! ethical ads via CodeFund This is a very basic “getting started with Webpack” guide for use with Webpack v3. This doesnʼt cover all features, but it should get you started in understanding the config file format. Basic config webpack.config.js module.exports = { context: __dirname, entry: 'src/app.js', output: { path: __dirname + '/public', filename: 'app.js' } } Terminal npm install --save-dev webpack webpack build webpack -- -p build production webpack -- --watch compile continuously This compiles src/app.js into public/app.js. (Note: you may need to use ./node_modules/.bin/webpack as a command if youʼre not invoking Webpack via npm scripts.) Multiple files webpack.config.js module.exports = { entry: { app: 'src/app.js', vendor: 'src/vendor.js' }, output: { path: __dirname + '/public', filename: '[name].js' } } This creates app.js and vendor.js. # Loaders Babel Terminal npm install --save-dev \ babel-loader \ babel-preset-env \ babel-preset-react webpack.config.js module.exports = { ··· module: { rules: [ { test: /\.js$/, exclude: /node_modules/, use: [ { loader: 'babel-loader' } ] } ] } } .babelrc { "presets": [ "env", "react" ] } Adds support for Babel. CSS Terminal npm install --save-dev \ css-loader \ style-loader webpack.config.js module.exports = { ··· module: { rules: [ { test: /\.css$/, exclude: /node_modules/, use: [ { loader: 'style-loader' }, { loader: 'css-loader'
    [Show full text]
  • Open Source Licenses Visionize Lab Suite the Software of Visionize Lab Suite Contains Open Source Licenses Included in This Document
    Open Source Licenses VisioNize Lab Suite The software of VisioNize Lab Suite contains open source licenses included in this document. Package name License Website/Repository Publisher/Author @angular-devkit/[email protected] MIT https://github.com/angular/angular-cli Angular Authors @angular-devkit/[email protected] MIT https://github.com/angular/angular-cli Angular Authors @angular-devkit/build-optimiz- MIT https://github.com/angular/angular-cli Angular Authors [email protected] @angular-devkit/build-web- MIT https://github.com/angular/angular-cli Angular Authors [email protected] @angular-devkit/[email protected] MIT https://github.com/angular/angular-cli Angular Authors @angular-devkit/[email protected] MIT https://github.com/angular/angular-cli Angular Authors @angular/[email protected] MIT https://github.com/angular/angular angular @angular/[email protected] MIT https://github.com/angular/angular-cli Angular Authors @angular/[email protected] MIT https://github.com/angular/angular angular @angular/[email protected] MIT https://github.com/angular/angular @angular/[email protected] MIT https://github.com/angular/angular angular @angular/[email protected] MIT https://github.com/angular/angular angular @angular/[email protected] MIT https://github.com/angular/angular angular @angular/[email protected] MIT https://github.com/angular/angular angular @angular/platform-browser-dynam- MIT https://github.com/angular/angular angular [email protected] @angular/[email protected] MIT https://github.com/angular/angular angular @angular/[email protected] MIT https://github.com/angular/angular angular
    [Show full text]
  • Automated Large-Scale Multi-Language Dynamic Program
    Automated Large-Scale Multi-Language Dynamic Program Analysis in the Wild Alex Villazón Universidad Privada Boliviana, Bolivia [email protected] Haiyang Sun Università della Svizzera italiana, Switzerland [email protected] Andrea Rosà Università della Svizzera italiana, Switzerland [email protected] Eduardo Rosales Università della Svizzera italiana, Switzerland [email protected] Daniele Bonetta Oracle Labs, United States [email protected] Isabella Defilippis Universidad Privada Boliviana, Bolivia isabelladefi[email protected] Sergio Oporto Universidad Privada Boliviana, Bolivia [email protected] Walter Binder Università della Svizzera italiana, Switzerland [email protected] Abstract Today’s availability of open-source software is overwhelming, and the number of free, ready-to-use software components in package repositories such as NPM, Maven, or SBT is growing exponentially. In this paper we address two straightforward yet important research questions: would it be possible to develop a tool to automate dynamic program analysis on public open-source software at a large scale? Moreover, and perhaps more importantly, would such a tool be useful? We answer the first question by introducing NAB, a tool to execute large-scale dynamic program analysis of open-source software in the wild. NAB is fully-automatic, language-agnostic, and can scale dynamic program analyses on open-source software up to thousands of projects hosted in code repositories. Using NAB, we analyzed more than 56K Node.js, Java, and Scala projects. Using the data collected by NAB we were able to (1) study the adoption of new language constructs such as JavaScript Promises, (2) collect statistics about bad coding practices in JavaScript, and (3) identify Java and Scala task-parallel workloads suitable for inclusion in a domain-specific benchmark suite.
    [Show full text]
  • Jiho£Eská Univerzita V Ƒeských Bud¥Jovicích Postcss a Cssnext Jako
    Jiho£eská univerzita v eských Bud¥jovicích Pedagogická fakulta Katedra informatiky PostCSS a cssnext jako nástroje pro transformaci a modularitu CSS JavaScriptem PostCSS and cssnext, tools enabling transformation and modularity of CSS using JavaScript Bakalá°ská práce Vypracoval: Jakub Jetleb Vedoucí práce: PaedDr. Petr Pexa, Ph.D. eské Bud¥jovice 2018 Prohlá²ení Prohla²uji, ºe svoji bakalá°skou práci jsem vypracoval samostatn¥ pouze s po- uºitím pramen· a literatury uvedených v seznamu citované literatury. Prohla²uji, ºe v souladu s 47b zákona £. 111/1998 Sb. v platném zn¥ní sou- hlasím se zve°ejn¥ním své bakalá°ské práce, a to v nezkrácené podob¥ elektro- nickou cestou ve ve°ejn¥ p°ístupné £ásti databáze STAG provozované Jiho£es- kou univerzitou v eských Bud¥jovicích na jejích internetových stránkách, a to se zachováním mého autorského práva k odevzdanému textu této kvalika£ní práce. Souhlasím dále s tím, aby toutéº elektronickou cestou byly v souladu s uvedeným ustanovením zákona £. 111/1998 Sb. zve°ejn¥ny posudky ²kolitele a oponent· práce i záznam o pr·b¥hu a výsledku obhajoby kvalika£ní práce. Rovn¥º souhlasím s porovnáním textu mé kvalika£ní práce s databází kvali- ka£ních prací Theses.cz provozovanou Národním registrem vysoko²kolských kvalika£ních prací a systémem na odhalování plagiát·. V eských Bud¥jovicích dne 8. £ervence 2018. Abstrakt/Anotace Cílem bakalá°ské práce je zpracovat problematiku nástroj· PostCSS a CSSnext, které jsou ur£eny pro transformaci a modularitu CSS JavaScriptem vyuºitím prom¥nných a vkládaných import·. Tyto nástroje usnad¬ují práci p°i tvorb¥ front-end webových aplikací, díky standardizované syntaxi a modularit¥ nap°.
    [Show full text]
  • Resume.Pages
    Peter Ramsing https://peter.coffee | github.com/peterramsing [email protected] | (541) 231-3620 | Portland, Oregon A determined software developer, with a focus on web applications, marketing site development, business strategy, and software team leadership. Peter offers a unique skillset with experience maintaining the largest CSS grid for PostCSS, developing large-scale web applications, and jump-starting software teams to perform beyond expectations. Key Skills • Component-based AngularJS (1.x) along with plain javascript objects for portable logic • Well tested Object-Oriented javascript based on TDD and UML • Extremely skilled in producing maintainable CSS using plain CSS or pre/post-processors • Problem-solving against rapid deadlines and collaborating on innovative solutions • ES5 and ES6 Javascript using Babel or non-bundled javascript • Providing compliant HTML using a11y standards promoting best practices • Working with projects through the entire lifecycle from inception to quantifying success and optimizing after release • Well versed in modern HTML with the ability to write extremely maintainable markup • Experienced with leading and participating in both Waterfall and Agile methodologies • Open to rapid and fast-paced changes with constantly evolving business targets and web toolsets Front-end CSS • SCSS, LESS, Stylus, PostCSS, Bootstrap, Foundation, Susy, Flexbox, CSS Grid, Float-based grids Javascript • ES5, ES6, AngularJS, React, Angular, Ember, AVA, Chai, Jasmine, Tooling • Gulp, Webpack, Browserify, PostCSS, Jekyll Backend Node • Express, Version 4 - 8, Python • Django, Django Rest Framework Tooling • Jenkins CI, Travis CI, Git, GitHub, BitBucket, GitLab, NPM Work Experience Software Developer October 2016 - Current Veelo - Portland, Oregon • Implements complex CSS layout designs in performant ways ensuring a11y compliance.
    [Show full text]
  • Brno University of Technology a Converter
    BRNO UNIVERSITY OF TECHNOLOGY VYSOKÉ UČENÍ TECHNICKÉ V BRNĚ FACULTY OF INFORMATION TECHNOLOGY DEPARTMENT OF INTELLIGENT SYSTEMS FAKULTA INFORMAČNÍCH TECHNOLOGIÍ ÚSTAV INTELIGENTNÍCH SYSTÉMŮ A CONVERTER BETWEEN THE LESS AND SASS STYLESHEET FORMATS PŘEKLADAČ MEZI FORMÁTY LESS A SASS BACHELOR’S THESIS BAKALÁŘSKÁ PRÁCE AUTHOR ATTILA VEČEREK AUTOR PRÁCE SUPERVISOR Prof. Ing. TOMÁŠ VOJNAR, Ph.D. VEDOUCÍ PRÁCE BRNO 2016 Abstract The aim of this thesis is to research the differences between the CSS preprocessor languages, namely Less and Sass, and find applicable transformation methods to implement a converter between their dynamic stylesheet formats. A general introduction to the concept of CSS preprocessors is provided first, which is followed by a thorough description of the Lessand Sass language features. In addition to this, all the discovered differences are stated and illustrative examples of the invented conversion methods are provided in this work. This is followed by the description of the design and implementation of the proposed converter. As a part of the contribution of this thesis, a CSS comparison tool based on abstract syntax tree transformation has also been developed. Its design is described along the testing procedure used to verify the invented conversion methods. The last part of the work summerizes the achieved results and the future directions of the converter. Abstrakt Cílem této bakalářské práce je výzkum rozdílů mezi CSS preprocesorovými jazyky, jmen- ovitě Less a Sass, a nalezení použitelných transormačních metod k implementaci překladače mezi jejich formáty. Nejprve je předložen koncept CSS preprocesorů a následuje detailní popis vlastností jazyků Less a Sass. V této práci jsou uvedené všechny zjištěné rozdíly, a pak jsou představeny nové konverzní metody s demonstrativními příklady.
    [Show full text]
  • CSS Processors Outline
    www.logicalimagination.training 800.657.1494 CSS Processors Course #: CSS102 Duration: 1 day Prerequisites A basic understanding of CSS. Details CSS Processors provides a practical and detailed introduction to the world of CSS processors. A CSS pre-processor is a program that takes the data of one language and converts the data into CSS upon compilation. A CSS post-processor takes existing CSS and refurbishes it to meet the standards of today's browsers. The modern landscape of CSS has been transformed by processors such as LESS, Sass, Stylus, PostCSS and others. The implementation of CSS processors in the workflow boosts efficiency and enforces the DRY (Don't Repeat Yourself) rule. Developers responsible for front-end development and CSS styling are the ideal audience for this course. Software Needed None. Outline CSS Processors Introduction to CSS Processors Overview of Pre-processors Overview of Post-processors The CSS Workflow Pros and Cons CSS Pre-processors LESS Sass Stylus CSS Post-processors PostCSS Pleeease Stylecow Garden (Clojure) Features and Functionality Syntax Variables Nesting Mixins Inheritance Importing Color Functions Operations Prefixes Fallbacks Minification Sourcemap Generators Single @media Rule A Deeper Look at PostCSS CSS Parser Abstract Syntax Tree (AST) CSS Generator Code Map Generator Autoprefixer CSSNext CSS Modules Font-Magician Stylelint PreCSS Choosing a CSS Workflow LESS vs. Sass vs. Stylus Using PostCSS with Plugins Using LESS, Sass or Stylus with PostCSS Full Clojure Stack: Clojure + ClojureScript + Garden.
    [Show full text]
  • CSS Procesori I Metodologije
    CSS procesori i metodologije Dumančić, Sebastijan Master's thesis / Diplomski rad 2017 Degree Grantor / Ustanova koja je dodijelila akademski / stručni stupanj: Josip Juraj Strossmayer University of Osijek, Faculty of Electrical Engineering, Computer Science and Information Technology Osijek / Sveučilište Josipa Jurja Strossmayera u Osijeku, Fakultet elektrotehnike, računarstva i informacijskih tehnologija Osijek Permanent link / Trajna poveznica: https://urn.nsk.hr/urn:nbn:hr:200:028218 Rights / Prava: In copyright Download date / Datum preuzimanja: 2021-09-25 Repository / Repozitorij: Faculty of Electrical Engineering, Computer Science and Information Technology Osijek SVEUČILIŠTE JOSIPA JURJA STROSSMAYERA U OSIJEKU FAKULTET ELEKTROTEHNIKE, RAČUNARSTVA I INFORMACIJSKIH ZNANOSTI Sveučilišni studij CSS procesori i metodologije Diplomski rad Sebastijan Dumančić Osijek, 2017. SADRŽAJ 1. UVOD CSS PROCESORE I METODOLOGIJU ................................................................................ 1 2. POVIJEST I RAZVOJ CSS-A .............................................................................................................. 2 2.1. Povijest ........................................................................................................................................ 2 2.2. W3C ............................................................................................................................................. 3 2.3. Internet preglednici .....................................................................................................................
    [Show full text]
  • Notices: License License Text Libraries Copyright Notices
    This application uses certain open source software. As required by the terms of the open source license applicable to such open source software, we are providing you with the following notices: License License Text Libraries Copyright Notices ISC ISC License Copyright (c) 2004-2010 by Internet abab-1.0.4.tgz Copyright © 2019 W3C and Jeff Carpenter Systems Consortium, Inc. ("ISC") Copyright (c) Isaac Z. Schlueter and Copyright (c) 1995-2003 by Internet Software abbrev-1.1.1.tgz Consortium Contributors Copyright Isaac Z. Schlueter Permission to use, copy, modify, and /or distribute anymatch-2.0.0.tgz Copyright 2014 Elan Shanker this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all Copyright 2019 Elan Shanker, Paul Miller anymatch-3.1.1.tgz copies. (https://paulmillr.com) THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING aproba-1.2.0.tgz Copyright 2015 Rebecca Turner ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY are-we-there-yet-1.1.5.tgz Copyright 2015 Rebecca Turner SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, ast-types-flow-0.0.7.tgz Copyright (c) 2018 Kyle Davis NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. block-stream-0.0.9.tgz Copyright Isaac Z Copyright Isaac
    [Show full text]
  • Icount 4.5.1 Front End Open Source Component June 2021
    iCount 4.5.1 Front End Open Source Component June 2021 This application uses certain open source software. As required by the terms of the open source license applicable to such open source software, we are providing you with the following notices: License License Text Libraries Copyright Notices MIT MIT License Copyright (c) <year> <copyright holders> JSONStream-1.3.5.tgz Copyright 2011 Dominic Tarr Permission is hereby granted, free of charge, to any Copyright 2014 Jonathan Ong Copyright 2015 person obtaining a copy of this software and accepts-1.3.7.tgz associated documentation files (the "Software"), to Douglas Christopher Wilson deal in the Software without restriction, including without limitation the rights to use, copy, modify, Copyright 2012-2018 by various contributors (see acorn-6.4.1.tgz merge, publish, distribute, sublicense, and/or sell AUTHORS) copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: Copyright 2012 Another-D-Mention Software and adm-zip-0.4.16.tgz other contributors, The above copyright notice and this permission notice (including the next paragraph) shall be included in all copies or substantial portions of the Software. after-0.8.2.tgz Copyright 2011 Raynos THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF agent-base-4.2.1.tgz Copyright 2013 Nathan Rajlich ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO agent-base-4.3.0.tgz Copyright 2013 Nathan Rajlich EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, Copyright 2012-2015 fengmk2 Copyright 2012- agentkeepalive-3.5.2.tgz ARISING FROM, OUT OF OR IN CONNECTION WITH THE 2015 fengmk2 SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
    [Show full text]
  • The HCL License Agreement and Any Applicable Information on the Web
    The HCL license agreement and any applicable information on the web download page for HCL products refers Licensee to this file for details concerning notices applicable to code included in the products listed above ("the Program"). Notwithstanding the terms and conditions of any other agreement Licensee may have with HCL or any of its related or affiliated entities (collectively "HCL"), the third party code identified below is subject to the terms and conditions of the HCL license agreement for the Program and not the license terms that may be contained in the notices below. The notices are provided for informational purposes. Please note: This Notices file may identify information that is not used by, or that was not shipped with, the Program as Licensee installed it. IMPORTANT: HCL does not represent or warrant that the information in this NOTICES file is accurate. Third party websites are independent of HCL and HCL does not represent or warrant that the information on any third party website referenced in this NOTICES file is accurate. HCL disclaims any and all liability for errors and omissions or for any damages accruing from the use of this NOTICES file or its contents, including without limitation URLs or references to any third party websites. <<Begin Lifecycle StarterKit Notices>> <<Begin SSA / Self-Service Application Notices>> License Library Copyrights Description License Reference Reference Type Homepage Download Link Apache 2.0 aws-sign2- 0.7.0.tgz AWS signing. Originally pulled from LearnBoost/knox, maintained as vendor in request, now a standalone module. https://www.npmjs.org/package/aws-sign2 NPM (details available in Node Package Manager) https://github.com/mikeal/aws-sign#readme https://registry.npmjs.org/aws-sign2/-/aws-sign2-0.7.0.tgz Apache 2.0 caseless-0.12.0.tgz Caseless object set/get/has, very useful when working with HTTP headers.
    [Show full text]