angular-rollup - npm Package Versions

2.0.0-rc.5

• FIXED issues with --env in development build
• FIXED issue that didnt set the environment by default to prod in prod build
• UPDATE main.ts to compile using module and target from tsconfig

2.0.0-rc.4

• NEW --prettier argument to scaffold a new app with prettier and installs a precommit hook
• NEW --ssl argument to scaffold a new app with https express server
• DEPRECATED main.ts, use @angular/cli supplied src/main.ts instead
• FIXED issue that prevented library build from compiling global sass

NOTE: Running the https express server requires a public key and certificate. Generate key.pem and cert.pem and save in the backend directory.

2.0.0-rc.3

• BREAKING CHANGE ngr.config.js must be updated to latest schema to support multiple projects in the same build
• NEW projects in ngr.config.js mirrors @angular/cli handling of multiple projects
• NEW cli command for library build allows user to leave out --config cli argument
• FIXED issue that caused error messages to hang in console after TypeScript compiles without errors
• FIXED issue that caused some errors not to produce a stacktrace
• FIXED issue that caused library builds to not export css properly
• FIXED issue that caused new projects to not replace the <title> tag properly
• FIXED issue when logging library builds without any global styles
• FIXED issue that caused node > 9.0.0 to display SIGNIT error message
• FIXED issue that prevented dev build from displaying stats at end
• UPDATE package to support >8.0.0 <10.0.0

NOTE: This version contains breaking changes due to the new addition of projects in ngr.config.js.

To migrate an existing src directory:

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

2.0.0-rc.2

• NEW spinners and emojis in logs
• FIXED several issues with logs including output in VS Code
• FIXED issue that prevented app from scaffolding
• FIXED potential issues from files not being copied from existing @angular/cli project

2.0.0-rc.1

• NEW migrate a @angular/cli^6.0.0 project to angular-rollup
• NEW generate a library with ngr generate library lib-name in any project directory
• FIXED issues with watcher when running ngr build dev --watch
• FIXED issues when running ngr new
• UPDATE CHANGELOG.md with RC changes

2.0.0-rc.0

• NEW --rollup and --webpack arguments for ngr build prod
• NEW Rollup build optimizes with Closure Compiler in ADVANCED_OPTIMIZATIONS
• NEW buildHooks in dev build for watching filesystem changes
• NEW postcss.config.js configuration to match the latest postcss-cli@5.0.0
• NEW environment variables, uses same --env argument as @angular/cli
• NEW README.md details changes in the angular-rollup project
• NEW out-css directory in root stores temporary sass output
• NEW production build concatenates vendor files in vendor.js
• NEW --src property will migrate src and config from existing angular-rollup projects to help in the upgrade process
• NEW integrate Angular Build Optimizer in production builds
• FIXED several issues with @angular/cli integration
• FIXED several issues when configuring postcss plugins
• FIXED issues with sass compile when the file contains underscore
• FIXED several issues with logs
• CHANGE removed duplicate config in ngr.config.js, now defaults to angular.json
• DEPRECATED build folder, now builds are output in dist/{{projectName}}

UPDATE

The easiest way to update an existing angular-rollup project is to create a new application and migrate the existing config and src.

BREAKING CHANGE

• REMOVE config/postcss.*.js and convert to postcss.config.js with environment variables

TIP

Configure your tsconfig.json to exclude the new out-tsc and out-css directories.

FILESYSTEM WATCHER

In ngr.config.js you can listen for changes in the src or dist folders and do something on change.

module.exports = {
    buildHooks: {
        dev: {
            post: () => {
                spawn('node_modules/.bin/rollup', ['-c', 'rollup.config.dev.js'],
                    { stdio: 'inherit', shell: true });
            },
            watch: {
                dist: (filePath) => {
                    if (!filePath.includes('bundle.js') &&
                         filePath.includes('.js')) {
                        spawn('node_modules/.bin/rollup', ['-c', 'rollup.config.dev.js'],
                            { stdio: 'inherit', shell: true});
                    }
                }
            }
        },

2.0.0-beta.1

• Support Angular 6.0.0-rc. Apps scaffolded in 2.0.0 will default to 6.0.0 once it is released.
• Support building libraries with Package Format 6.0
• Moved configuration files for library packages to config directory to clean up source
• Fixed issue that prevented logs from displaying libraries that are copied
• Resequenced development build making it faster for large scale projects
• Development build doesnt clean build folder by default, use --clean flag when coming from prod build
• Streamline file copy tasks
• Fix issue preventing files in public directory from being copied in --watch mode

2.0.0-beta.0

• All new build architecture allows for easier maintainance, human readibility
• 4x faster builds in some cases
• Fixed an issue that prevented styles from compiling in library builds

IMPROVEMENTS

• Add src/style/**/*.scss and src/style/**/*.css to excludes Array in tsconfig.dev.json. This will force ngc to ignore global styles and prevent compilation. Updates to global styling can now happen without browser reload.
• Deprecated requirement for Babel in library build

BREAKING CHANGES

• main.js, main.prod.js and main.prod.ts are now deprecated. These files can be removed. The build now automatically handles main.ts for dev and jit builds.
• Upgrade rollup to ^0.55.0. The library build now supports input and output syntax by default
• Arguments passed to buildHooks and server.js may change, please check and update where necessary

For example, in previous scaffolds server.js contained this conditional checking for --watch but canWatch supposes there is an =. In 2.0.0 only watch is exposed, not anything after the =:

BEFORE:

  if (arg.includes('watch')) {
    canWatch = arg.split('=')[1].trim() === 'true' ? true : false;
  }

AFTER:

  if (arg.includes('watch')) {
    canWatch = true;
  }

• Change the model for declaring library packages in ngr.config.js. The new config should look like this:

BEFORE:

dep: {
    lib: [],
    prodLib: []
}

AFTER:

lib: {
    dev: [],
    prod: []
}

1.0.8

• Fixed issue that prevented post buildHook from firing in dev build
• Fixed timing issues when logging the dev build

1.0.7

• Added --env argument for build command
• Added rxjs/Subscription to default paths mapped in system.config.js

In this release, angular/rollup will pass an environment variable to process.argv. Below is an example of how you could use environment variables with a pattern similar to @angular/cli with ngr.config.js. angular-rollup gives you control over how you implement environment variables. Copy the current environment file into the src/app folder or any other folder you desire so it can be imported into source code.

buildHooks: {
        prod: {
            pre: (argv) => {
                var env = argv.find(a => a.includes('env')).split('=')[1];
                return new Promise((res, rej)=>{
                    cp('environments/environment.'+env+'.ts', 'src/app/environment.ts');
                    res();
                });
            }
        }
}