PHPackages                             packagefactory/atomicfusion-jscomponents - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. packagefactory/atomicfusion-jscomponents

AbandonedArchivedNeos-package[Utility & Helpers](/categories/utility)

packagefactory/atomicfusion-jscomponents
========================================

Augment Fusion components to ease initialization with JavaScript

v2.0.0(8y ago)12.9k1GPL-3.0PHP

Since Jan 24Pushed 8y agoCompare

[ Source](https://github.com/PackageFactory/atomic-fusion-js-components)[ Packagist](https://packagist.org/packages/packagefactory/atomicfusion-jscomponents)[ RSS](/packages/packagefactory-atomicfusion-jscomponents/feed)WikiDiscussions master Synced 5d ago

READMEChangelog (2)Dependencies (2)Versions (3)Used By (0)

PackageFactory.AtomicFusion.JsComponents
========================================

[](#packagefactoryatomicfusionjscomponents)

> Augment Fusion components to ease initialization with JavaScript

Why?
----

[](#why)

TBD.

Usage
-----

[](#usage)

TBD.

Example Runtime
---------------

[](#example-runtime)

TBD.

Discovery of JavaScript files
-----------------------------

[](#discovery-of-javascript-files)

Fusion actually holds no information about the file a prototype is defined in. So, to enable the discovery of files put alongside those component \*.fusion files, we need to configure a lookup pattern:

```
PackageFactory:
  AtomicFusion:
    JsComponents:
      tryFiles:
        - resource://{packageKey}/Private/Fusion/{componentPath}.js
```

With the above configuration the JS file for the prototype `prototype(Vendor.Site:MyAwesomeComponent)` will be assumed as `resource://Vendor.Site/Private/Fusion/MyAwesomeComponent.js`.

`{packageKey}` and `{componentPath}` are variables that will be replaced with runtime information of the respective fusion prototype.

The following variables are considered:

- `{prototypeName}` - The entire prototype name
- `{packageKey}` - The part of the prototype name before the `:`
- `{componentName}` - The part of the prototype name after the `:`
- `{componentBaseName}` - The last part of the componentName, if seperated by dots (for `Vendor.Site:Atom.Button` that would be: `Button`)
- `{componentPath}` - Similar to `{componentName}` with all dots being replaced by Directory Separators.

By default, the package looks at the following patterns:

```
resource://{packageKey}/Private/Fusion/{componentPath}.js
resource://{packageKey}/Private/Fusion/{componentPath}/{componentBaseName}.js
resource://{packageKey}/Private/Fusion/{componentPath}/index.js
resource://{packageKey}/Private/Fusion/{componentPath}/Index.js
resource://{packageKey}/Private/Fusion/{componentPath}/component.js
resource://{packageKey}/Private/Fusion/{componentPath}/Component.js

```

Caveats
-------

[](#caveats)

Recently, the native component prototype `Neos.Fusion:Component` has arrived in the Neos.Fusion core. Unfortunately, this package won't work with this new prototype and relies on `PackageFactory.AtomicFusion:Component` to be present.

This will likely change in the future, either through this package or a PR to Neos.Fusion.

If you still want to use this package with an existing code base, that relies on `Neos.Fusion:Component`, you could replace the `Neos.Fusion:Component` standard implementation with the one for `PackageFactory.AtomicFusion:Component`:

```
prototype(Neos.Fusion:Component) {
    @class = 'PackageFactory\\AtomicFusion\\FusionObjects\\ComponentImplementation'
}

```

`PackageFactory.AtomicFusion:Component` is fully compatible to `Neos.Fusion:Component`, but you should be nonetheless aware:

*THIS IS NOT THE JEDI WAY!*

License
-------

[](#license)

see [LICENSE.md](./LICENSE.md)

###  Health Score

31

—

LowBetter than 68% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity19

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity64

Established project with proven stability

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~112 days

Total

2

Last Release

2923d ago

Major Versions

v1.0.0 → v2.0.02018-05-16

### Community

Maintainers

![](https://www.gravatar.com/avatar/1159e78bff9c03cc5ed626447ca5072097107f58af459a9b8bac8d933ba8298c?d=identicon)[wilhelm.behncke](/maintainers/wilhelm.behncke)

---

Top Contributors

[![grebaldi](https://avatars.githubusercontent.com/u/2522299?v=4)](https://github.com/grebaldi "grebaldi (5 commits)")

### Embed Badge

![Health badge](/badges/packagefactory-atomicfusion-jscomponents/health.svg)

```
[![Health](https://phpackages.com/badges/packagefactory-atomicfusion-jscomponents/health.svg)](https://phpackages.com/packages/packagefactory-atomicfusion-jscomponents)
```

###  Alternatives

[neos/neos

An open source Content Application Platform based on Flow. A set of core Content Management features is resting within a larger context that allows you to build a perfectly customized experience for your users.

116989.0k674](/packages/neos-neos)[neos/eel

The Embedded Expression Language (Eel) is a building block for creating Domain Specific Languages

122.0M27](/packages/neos-eel)[neos/fusion-form

Fusion Form

19724.3k31](/packages/neos-fusion-form)[neos/form

Extensible and flexible API for building web forms

18853.0k40](/packages/neos-form)[avency/neos-vardump

Neos VarDump Package

147.1k](/packages/avency-neos-vardump)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)