angular2-rollup - npm Package Versions

2.0.2

• UPDATE running ngr in non angular-rollup project will display error in console once again
• FIXED issue that caused libraries to scaffold with incorrect path to es5 bundle
• FIXED issue that caused libraries to not generate properly with a scoped name
• FIXED issue that prevented production build when building rxjs FESM
• FIXED issues that prevents JIT build from executing
• FIXED issue that prevents PROD build from completing properly

2.0.1

• UPDATE scaffold for @angular packages > 7.0.0
• UPDATE production and library builds to support .scss filenames in component.ts files
• UPDATE production build to support css only
• FIXED issues in library build when using .css files instead of .scss

NOTE: In this release we made it possible to develop easier with @angular/cli yet still build for production with ngr build prod. The existing development build still works, but it is highly recommended to use ng serve for development when possible instead of ngr build dev. If you have been developing off angular/rollup, upgrading to take advantage of ng serve is relatively simple. Update all references to .css files in your component.ts files to .scss. Now your application should run fine in @angular/cli for development and the angular-rollup production build will still honor SCSS for production.

2.0.0

angular-rollup 2.0.0 delivers the same cli as 1.x with more powerful builds and integration with @angular/cli!

• NEW integration with @angular/cli means you can run familiar commands in same project
• NEW configuration means less files in root directory
• NEW asynchronous build scripts deliver faster build times
• NEW ability to work with several libraries in the same project
• NEW logging mechanism destroys the log on every message
• NEW pretty printed error logs in Terminal with direct links to VS Code
• NEW ability to scaffold a project with prettier installed
• NEW ability to scaffold a project with SSL enabled in development server
• NEW ability to migrate an application generated with @angular/cli to angular-rollup
• NEW production build is even more optimal with inclusion of Angular Build Optimizer
• NEW scaffold a new project with Angular IVY preconfigured
• NEW stacktraces when ngr fails allowing for more better error reporting
• NEW --env argument mirrors the way @angular/cli handles environments
• NEW build hooks for development build allow you to watch changes in src or dist in ngr.config.js
• NEW production build concatenates all vendor scripts into vendor.js cutting down network requests
• UPDATED postcss to > 5.0.0, including new configuration with the postcss-cli
• UPDATED --rollup argument will bundle with Rollup like before but now optimizes with Closure Compiler in ADVANCED_OPTIMIZATIONS
• DEPRECATED build directory, all builds are now output to dist by default comparable to @angular/cli
• DEPRECATED the ability to scaffold an Angular Universal application. This feature will return soon!
• DEPRECATED the ability to lazyload with Closure Compiler. This feature will return soon!
• DEPRECATED main.ts. The build now uses the main.ts provided by @angular/cli
• DEPRECATED unit / e2e testing scripts, use @angular/cli instead
• DEPRECATED i18n tooling, use @angular/compiler-cli directly instead

UPDATING from 1.x to @angular/cli

To migrate an application running on angular-rollup 1.x or @angular/cli, the best option is to scaffold a new app with the old source.

ngr new my-new-app --src /path/to/old/src

This will migrate the src directory as well as all config from the old project to a new directory. Old configuration files will be renamed .bak so you can compare old files against the new configuration.

ROADMAP

These tasks didn't make the 2.0.0 release but are items I really want to include in future releases!

• Scaffold Angular Universal application
• Scripts for codesplitting an application to optimize lazy loaded bundles with Closure Compiler
• Generate Bazel configuration in the project
• Support for LESS, Stylus, CSS only workflows