v3.2.0

This release includes fixes for issues related to deferred scripts.

• Corrects domContentLoaded so it doesn't execute the callback more than once
• Adds a new true option for config.load

v3.1.0

Added

• Adds support for a custom selector via the config.root property

Fixed

• Component elements are collected from within the function created by componentProvider
• domContentLoaded now checks for an interactive document readyState
• Importing from v2/ will now work correctly

v3.0.0

This is a reimagining of the framework that removes unused features, decreases bundle sizes, simplifies our component structure, and speeds up code execution.

Greater flexibility

Components can now be either a class or a function, with the revised framework centered around componentProvider, which collects a component’s properties and automatically initializes it based on its configuration.

Faster execution

With relatively minor updates, existing projects can reap the benefits as well. This is because the framework no longer writes to window.manifest, which required a limiter. With that limiter removed, our components are initialized without any delay. You will notice the difference!

---

Changes

Added

• Adds componentProvider for initializing and loading components
• Adds componentLoader for optionally loading the function returned from componentProvider

Changed

• Simplifies component creation by allowing components to be a class or a function
• No longer writes to window[manifest]
• Replaces ComponentManager with initComponents for initializing legacy components using the /v2 export
• Moves Component to the /v2 export

Fixed

• Moves @babel/runtime to devDependencies

Removed

• Removes the rate limiter
• Removes Aria plugins; consider using aria-components instead.
• Removes the /core export due to code restructuring

ES module version

This release allows the js-component-framework to be imported into your project with ES Modules which can reduce the size of the bundled code.

v2.0.0

Version 2.0.0

This update reduces the frameworks footprint by providing the core functionality of the framework to be imported as a standalone library without the Aria plugins provided in src/plugins.

Users can import the core functionality by adding the /core to the import call:

// Import only the core component framework library.
import { Component } from 'js-component-framework/core';

NOTE:

The changes in this PR are compatible with previous versions and their configurations but will not provide the polyfills in previous versions as IE support has been dropped.

Summary of changes

• Reduce the size of the framework by adding a core/ directory which does not include the Aria plugins.
• Remove polyfills and support for IE
• update babel configs and plugins
• update ESLint config and include Airbnb standards
• Bump to major version.

Security Updates

Automated security updates

v1.2.5

• UPDATE rate limiter to standalone function.
• REMOVE Bottleneck library

v1.2.4

• Automated security updates

v1.2.2

• FIX bottleneck updates caused missing polyfills and non-transpiled code
• UPDATE bottleneck package to latest
• ADD babel polyfills and plugins relative to bottleneck package update.
• ADD browserlist settings to package.json

v1.2.1

FIXED: Bugs related to the hasTransition option for AriaPlugin