It is what it says it is.
However, this bundler aims to be a monolithic does-it-all type of bundler; with zero configuration needed. (however, optional configuration will be supported)
- A bundler should not need excessive attention.
- A bundler should not get in the way of a developers workflow.
- A bundler should be fast.
- A bundler should not be written in JavaScript / Node.
- Commonly used features among JS developers should be supported out of the box.
- The output of the bundler should work everywhere. (to an extent which is possible of course)
Most bundlers allows you to select an output format of the code, such as:
"CommonJS", "AMD", "System", "UMD", "ES6", "ES2015" or "ESNext"
FJB does not implement this concept.
Instead, FJB adapts the code automatically through static analysis.
FJB aims to generate code that works everywhere (when possible).
A bundler should be smart enough so that the developer can focus on other things. 🧠
fjb index.js -o dist.js
- Being fast
- ES6 module imports / exports
- Aliased imports
- Wildcard imports
- JSX support
- TypeScript support (currently unstable and under development)
- Importing JSON
- Importing CSS
- Importing & transpiling SCSS
- Automatic JSX format detection
- Plugin support
- Removing dead code (Tree shaking)
- Supports package.json
- Watchdog (
--watch
)
- Lazy imports
Below is an example of some code that is 100% supported.
(Without any plugins or configuration)
For more examples, have a look at:
To see benchmarks, have a look at benchmarks.md 🔥
You can also view them over at https://fjbundler.com
The easiest way to install FJB is to head over to releases and download a
.deb
file that suits you.
Then you can simply run:
sudo apt install ./<filename>.deb
To build
fjb
you will need the following:
- A C compiler (I would suggest gcc)
- Git
- Clone down the repository
- Run:
./build.sh
This step will generate a
fjb.out
executable file.
You can start using this right away. 🎩
To continue and install
fjb
globally: Run:
make install
Also make sure you add
$HOME/.local/bin
to your PATH.
https://unix.stackexchange.com/questions/26047/how-to-correctly-add-a-path-to-path
Have a look at benchmarks.md 🔥
Not sure, it's just a hobby project at this point.
Frustration, frustration with existing tools.
The existing alternatives are not fast enough, and gets in the way a bit more than they should.
You can definitely bundle React apps with FJB.
However, there might be some missing features / bugs since the JSX implementation in FJB is pretty new.
You can see a working React example here
I will not encourage anyone to use it, but feel free to do it.
Yes
Probably not, but feel free to make a pull-request with the required changes for it to work.
Probably. I haven't tried it, but I would definitely think so.
Yes you can. Simply fork it and start making pull-requests.
Have a look at this guide
No. I don't think JavaScript belongs in a bundler.
The reason why most bundlers today are slow, is because they are written in JavaScript.
If you find a bug, please report it here: https://github.com/sebbekarlsson/fjb/issues
Yes, but this feature is under development... so expect bugs.
There's no need to worry about that, FJB knows if you're using React or not, and automatically takes care of it for you.
GPL-3.0, LICENSE.md
Feel free to create an issue here, and I'll be able to help you.
I would prefer if you make pull-requests through forking at first.
Once I've seen that you've made valuable contributions, you might be able to be added as a collaborator.