Blade Script

A package to easily add transpiled & minified scripts to your blade components.

<button class="btn" onlick="myFunction()">{{ $slot }}</button><x-script>
functionmyFunction() {
// Do something.
}
</x-script>

Introduction

In case you want to add javascript functionality to a blade component, you can write it directly in the script tag. However, the script will then not be minified and if a component is used multiple times, the script tag will also be included multiple times.

Blade Script solves these problems. The javascript code can be minified in production and each script tag is only included once all without running a compiler separately. Also only required scripts are included.

Additionally there is the possibility to add transpilers like babel.

Installation

The package can be easily installed via composer.

composer require cbl/blade-script

Now the necessary assets must be published. This includes the script.php config and the storage folder where the compiled scripts are stored.

php artisan vendor:publish --provider="BladeScript\ServiceProvider"

Include Scripts

The blade component x-scripts includes all required scripts, so it may be placed at the very bottom of your body.

<body>
...
<x-scripts />
</body>

Usage

Each blade component can contain exactly one x-script component. Your scripts can then be written inside the wrapper like so.

<button class="btn" onlick="myFunction()">{{ $slot }}</button><x-script>
myFunction() {
// Do something.
}
</x-script>

Optimizing Scripts

Blade scripts share the same behavior as Views. As suggested in the View documentation, the script:cache command can be added to your deployment workflow to ensure that all scripts are compiled and thus improve performance.

php artisan script:cache

You may use the script:clear command to clear the script cache:

php artisan script:clear

Write Transpiler

You can easily add transpilers to the compiler, the following example explains how to create and include a transpiler.

First you have to create a transpiler class that implements the BladeScript\Contracts\Transpiler contract.

namespaceBladeBabel;
useBabel\TranspilerasBabel;
useBladeScript\Contracts\Transpiler;
class BabelTranspiler implements Transpiler
{
publicfunctiontranspile($script)
{
return Babel::transform($script);
}
}

The transpiler can now be added to the compiler in your service provider like so:

namespaceBladeBabel;
useIlluminate\Support\ServiceProvider;
class BabelServiceProvider extends ServiceProvider
{
publicfunctionregister()
{
$this->app->afterResolving('script.compiler', function ($compiler) {
$compiler->addTranspiler(newBabelTranspiler);
});
}
}

Blade Script

A package to easily add transpiled & minified scripts to your blade components.

<button class="btn" onlick="myFunction()">{{ $slot }}</button><x-script>
functionmyFunction() {
// Do something.
}
</x-script>

Introduction

In case you want to add javascript functionality to a blade component, you can write it directly in the script tag. However, the script will then not be minified and if a component is used multiple times, the script tag will also be included multiple times.

Blade Script solves these problems. The javascript code can be minified in production and each script tag is only included once all without running a compiler separately. Also only required scripts are included.

Additionally there is the possibility to add transpilers like babel.

Installation

The package can be easily installed via composer.

composer require cbl/blade-script

Now the necessary assets must be published. This includes the script.php config and the storage folder where the compiled scripts are stored.

php artisan vendor:publish --provider="BladeScript\ServiceProvider"

Include Scripts

The blade component x-scripts includes all required scripts, so it may be placed at the very bottom of your body.

<body>
...
<x-scripts />
</body>

Usage

Each blade component can contain exactly one x-script component. Your scripts can then be written inside the wrapper like so.

<button class="btn" onlick="myFunction()">{{ $slot }}</button><x-script>
myFunction() {
// Do something.
}
</x-script>

Optimizing Scripts

Blade scripts share the same behavior as Views. As suggested in the View documentation, the script:cache command can be added to your deployment workflow to ensure that all scripts are compiled and thus improve performance.

php artisan script:cache

You may use the script:clear command to clear the script cache:

php artisan script:clear

Write Transpiler

You can easily add transpilers to the compiler, the following example explains how to create and include a transpiler.

First you have to create a transpiler class that implements the BladeScript\Contracts\Transpiler contract.

namespaceBladeBabel;
useBabel\TranspilerasBabel;
useBladeScript\Contracts\Transpiler;
class BabelTranspiler implements Transpiler
{
publicfunctiontranspile($script)
{
return Babel::transform($script);
}
}

The transpiler can now be added to the compiler in your service provider like so:

namespaceBladeBabel;
useIlluminate\Support\ServiceProvider;
class BabelServiceProvider extends ServiceProvider
{
publicfunctionregister()
{
$this->app->afterResolving('script.compiler', function ($compiler) {
$compiler->addTranspiler(newBabelTranspiler);
});
}
}

Blade Script

A package to easily add transpiled & minified scripts to your blade components.

<button class="btn" onlick="myFunction()">{{ $slot }}</button><x-script>
functionmyFunction() {
// Do something.
}
</x-script>

Introduction

In case you want to add javascript functionality to a blade component, you can write it directly in the script tag. However, the script will then not be minified and if a component is used multiple times, the script tag will also be included multiple times.

Blade Script solves these problems. The javascript code can be minified in production and each script tag is only included once all without running a compiler separately. Also only required scripts are included.

Additionally there is the possibility to add transpilers like babel.

Installation

The package can be easily installed via composer.

composer require cbl/blade-script

Now the necessary assets must be published. This includes the script.php config and the storage folder where the compiled scripts are stored.

php artisan vendor:publish --provider="BladeScript\ServiceProvider"

Include Scripts

The blade component x-scripts includes all required scripts, so it may be placed at the very bottom of your body.

<body>
...
<x-scripts />
</body>

Usage

Each blade component can contain exactly one x-script component. Your scripts can then be written inside the wrapper like so.

<button class="btn" onlick="myFunction()">{{ $slot }}</button><x-script>
myFunction() {
// Do something.
}
</x-script>

Optimizing Scripts

Blade scripts share the same behavior as Views. As suggested in the View documentation, the script:cache command can be added to your deployment workflow to ensure that all scripts are compiled and thus improve performance.

php artisan script:cache

You may use the script:clear command to clear the script cache:

php artisan script:clear

Write Transpiler

You can easily add transpilers to the compiler, the following example explains how to create and include a transpiler.

First you have to create a transpiler class that implements the BladeScript\Contracts\Transpiler contract.

namespaceBladeBabel;
useBabel\TranspilerasBabel;
useBladeScript\Contracts\Transpiler;
class BabelTranspiler implements Transpiler
{
publicfunctiontranspile($script)
{
return Babel::transform($script);
}
}

The transpiler can now be added to the compiler in your service provider like so:

namespaceBladeBabel;
useIlluminate\Support\ServiceProvider;
class BabelServiceProvider extends ServiceProvider
{
publicfunctionregister()
{
$this->app->afterResolving('script.compiler', function ($compiler) {
$compiler->addTranspiler(newBabelTranspiler);
});
}
}

Blade Script

A package to easily add transpiled & minified scripts to your blade components.

<button class="btn" onlick="myFunction()">{{ $slot }}</button><x-script>
functionmyFunction() {
// Do something.
}
</x-script>

Introduction

In case you want to add javascript functionality to a blade component, you can write it directly in the script tag. However, the script will then not be minified and if a component is used multiple times, the script tag will also be included multiple times.

Blade Script solves these problems. The javascript code can be minified in production and each script tag is only included once all without running a compiler separately. Also only required scripts are included.

Additionally there is the possibility to add transpilers like babel.

Installation

The package can be easily installed via composer.

composer require cbl/blade-script

Now the necessary assets must be published. This includes the script.php config and the storage folder where the compiled scripts are stored.

php artisan vendor:publish --provider="BladeScript\ServiceProvider"

Include Scripts

The blade component x-scripts includes all required scripts, so it may be placed at the very bottom of your body.

<body>
...
<x-scripts />
</body>

Usage

Each blade component can contain exactly one x-script component. Your scripts can then be written inside the wrapper like so.

<button class="btn" onlick="myFunction()">{{ $slot }}</button><x-script>
myFunction() {
// Do something.
}
</x-script>

Optimizing Scripts

Blade scripts share the same behavior as Views. As suggested in the View documentation, the script:cache command can be added to your deployment workflow to ensure that all scripts are compiled and thus improve performance.

php artisan script:cache

You may use the script:clear command to clear the script cache:

php artisan script:clear

Write Transpiler

You can easily add transpilers to the compiler, the following example explains how to create and include a transpiler.

First you have to create a transpiler class that implements the BladeScript\Contracts\Transpiler contract.

namespaceBladeBabel;
useBabel\TranspilerasBabel;
useBladeScript\Contracts\Transpiler;
class BabelTranspiler implements Transpiler
{
publicfunctiontranspile($script)
{
return Babel::transform($script);
}
}

The transpiler can now be added to the compiler in your service provider like so:

namespaceBladeBabel;
useIlluminate\Support\ServiceProvider;
class BabelServiceProvider extends ServiceProvider
{
publicfunctionregister()
{
$this->app->afterResolving('script.compiler', function ($compiler) {
$compiler->addTranspiler(newBabelTranspiler);
});
}
}

Blade Script

A package to easily add transpiled & minified scripts to your blade components.

<button class="btn" onlick="myFunction()">{{ $slot }}</button><x-script>
functionmyFunction() {
// Do something.
}
</x-script>

Introduction

In case you want to add javascript functionality to a blade component, you can write it directly in the script tag. However, the script will then not be minified and if a component is used multiple times, the script tag will also be included multiple times.

Blade Script solves these problems. The javascript code can be minified in production and each script tag is only included once all without running a compiler separately. Also only required scripts are included.

Additionally there is the possibility to add transpilers like babel.

Installation

The package can be easily installed via composer.

composer require cbl/blade-script

Now the necessary assets must be published. This includes the script.php config and the storage folder where the compiled scripts are stored.

php artisan vendor:publish --provider="BladeScript\ServiceProvider"

Include Scripts

The blade component x-scripts includes all required scripts, so it may be placed at the very bottom of your body.

<body>
...
<x-scripts />
</body>

Usage

Each blade component can contain exactly one x-script component. Your scripts can then be written inside the wrapper like so.

<button class="btn" onlick="myFunction()">{{ $slot }}</button><x-script>
myFunction() {
// Do something.
}
</x-script>

Optimizing Scripts

Blade scripts share the same behavior as Views. As suggested in the View documentation, the script:cache command can be added to your deployment workflow to ensure that all scripts are compiled and thus improve performance.

php artisan script:cache

You may use the script:clear command to clear the script cache:

php artisan script:clear

Write Transpiler

You can easily add transpilers to the compiler, the following example explains how to create and include a transpiler.

First you have to create a transpiler class that implements the BladeScript\Contracts\Transpiler contract.

namespaceBladeBabel;
useBabel\TranspilerasBabel;
useBladeScript\Contracts\Transpiler;
class BabelTranspiler implements Transpiler
{
publicfunctiontranspile($script)
{
return Babel::transform($script);
}
}

The transpiler can now be added to the compiler in your service provider like so:

namespaceBladeBabel;
useIlluminate\Support\ServiceProvider;
class BabelServiceProvider extends ServiceProvider
{
publicfunctionregister()
{
$this->app->afterResolving('script.compiler', function ($compiler) {
$compiler->addTranspiler(newBabelTranspiler);
});
}
}

Blade Script

A package to easily add transpiled & minified scripts to your blade components.

<button class="btn" onlick="myFunction()">{{ $slot }}</button><x-script>
functionmyFunction() {
// Do something.
}
</x-script>

Introduction

In case you want to add javascript functionality to a blade component, you can write it directly in the script tag. However, the script will then not be minified and if a component is used multiple times, the script tag will also be included multiple times.

Blade Script solves these problems. The javascript code can be minified in production and each script tag is only included once all without running a compiler separately. Also only required scripts are included.

Additionally there is the possibility to add transpilers like babel.

Installation

The package can be easily installed via composer.

composer require cbl/blade-script

Now the necessary assets must be published. This includes the script.php config and the storage folder where the compiled scripts are stored.

php artisan vendor:publish --provider="BladeScript\ServiceProvider"

Include Scripts

The blade component x-scripts includes all required scripts, so it may be placed at the very bottom of your body.

<body>
...
<x-scripts />
</body>

Usage

Each blade component can contain exactly one x-script component. Your scripts can then be written inside the wrapper like so.

<button class="btn" onlick="myFunction()">{{ $slot }}</button><x-script>
myFunction() {
// Do something.
}
</x-script>

Optimizing Scripts

Blade scripts share the same behavior as Views. As suggested in the View documentation, the script:cache command can be added to your deployment workflow to ensure that all scripts are compiled and thus improve performance.

php artisan script:cache

You may use the script:clear command to clear the script cache:

php artisan script:clear

Write Transpiler

You can easily add transpilers to the compiler, the following example explains how to create and include a transpiler.

First you have to create a transpiler class that implements the BladeScript\Contracts\Transpiler contract.

namespaceBladeBabel;
useBabel\TranspilerasBabel;
useBladeScript\Contracts\Transpiler;
class BabelTranspiler implements Transpiler
{
publicfunctiontranspile($script)
{
return Babel::transform($script);
}
}

The transpiler can now be added to the compiler in your service provider like so:

namespaceBladeBabel;
useIlluminate\Support\ServiceProvider;
class BabelServiceProvider extends ServiceProvider
{
publicfunctionregister()
{
$this->app->afterResolving('script.compiler', function ($compiler) {
$compiler->addTranspiler(newBabelTranspiler);
});
}
}

Blade Script

A package to easily add transpiled & minified scripts to your blade components.

<button class="btn" onlick="myFunction()">{{ $slot }}</button><x-script>
functionmyFunction() {
// Do something.
}
</x-script>

Introduction

In case you want to add javascript functionality to a blade component, you can write it directly in the script tag. However, the script will then not be minified and if a component is used multiple times, the script tag will also be included multiple times.

Blade Script solves these problems. The javascript code can be minified in production and each script tag is only included once all without running a compiler separately. Also only required scripts are included.

Additionally there is the possibility to add transpilers like babel.

Installation

The package can be easily installed via composer.

composer require cbl/blade-script

Now the necessary assets must be published. This includes the script.php config and the storage folder where the compiled scripts are stored.

php artisan vendor:publish --provider="BladeScript\ServiceProvider"

Include Scripts

The blade component x-scripts includes all required scripts, so it may be placed at the very bottom of your body.

<body>
...
<x-scripts />
</body>

Usage

Each blade component can contain exactly one x-script component. Your scripts can then be written inside the wrapper like so.

<button class="btn" onlick="myFunction()">{{ $slot }}</button><x-script>
myFunction() {
// Do something.
}
</x-script>

Optimizing Scripts

Blade scripts share the same behavior as Views. As suggested in the View documentation, the script:cache command can be added to your deployment workflow to ensure that all scripts are compiled and thus improve performance.

php artisan script:cache

You may use the script:clear command to clear the script cache:

php artisan script:clear

Write Transpiler

You can easily add transpilers to the compiler, the following example explains how to create and include a transpiler.

First you have to create a transpiler class that implements the BladeScript\Contracts\Transpiler contract.

namespaceBladeBabel;
useBabel\TranspilerasBabel;
useBladeScript\Contracts\Transpiler;
class BabelTranspiler implements Transpiler
{
publicfunctiontranspile($script)
{
return Babel::transform($script);
}
}

The transpiler can now be added to the compiler in your service provider like so:

namespaceBladeBabel;
useIlluminate\Support\ServiceProvider;
class BabelServiceProvider extends ServiceProvider
{
publicfunctionregister()
{
$this->app->afterResolving('script.compiler', function ($compiler) {
$compiler->addTranspiler(newBabelTranspiler);
});
}
}

Blade Script

A package to easily add transpiled & minified scripts to your blade components.

<button class="btn" onlick="myFunction()">{{ $slot }}</button><x-script>
functionmyFunction() {
// Do something.
}
</x-script>

Introduction

In case you want to add javascript functionality to a blade component, you can write it directly in the script tag. However, the script will then not be minified and if a component is used multiple times, the script tag will also be included multiple times.

Blade Script solves these problems. The javascript code can be minified in production and each script tag is only included once all without running a compiler separately. Also only required scripts are included.

Additionally there is the possibility to add transpilers like babel.

Installation

The package can be easily installed via composer.

composer require cbl/blade-script

Now the necessary assets must be published. This includes the script.php config and the storage folder where the compiled scripts are stored.

php artisan vendor:publish --provider="BladeScript\ServiceProvider"

Include Scripts

The blade component x-scripts includes all required scripts, so it may be placed at the very bottom of your body.

<body>
...
<x-scripts />
</body>

Usage

Each blade component can contain exactly one x-script component. Your scripts can then be written inside the wrapper like so.

<button class="btn" onlick="myFunction()">{{ $slot }}</button><x-script>
myFunction() {
// Do something.
}
</x-script>

Optimizing Scripts

Blade scripts share the same behavior as Views. As suggested in the View documentation, the script:cache command can be added to your deployment workflow to ensure that all scripts are compiled and thus improve performance.

php artisan script:cache

You may use the script:clear command to clear the script cache:

php artisan script:clear

Write Transpiler

You can easily add transpilers to the compiler, the following example explains how to create and include a transpiler.

First you have to create a transpiler class that implements the BladeScript\Contracts\Transpiler contract.

namespaceBladeBabel;
useBabel\TranspilerasBabel;
useBladeScript\Contracts\Transpiler;
class BabelTranspiler implements Transpiler
{
publicfunctiontranspile($script)
{
return Babel::transform($script);
}
}

The transpiler can now be added to the compiler in your service provider like so:

namespaceBladeBabel;
useIlluminate\Support\ServiceProvider;
class BabelServiceProvider extends ServiceProvider
{
publicfunctionregister()
{
$this->app->afterResolving('script.compiler', function ($compiler) {
$compiler->addTranspiler(newBabelTranspiler);
});
}
}

Name		Name	Last commit message	Last commit date
.github/workflows		.github/workflows
config		config
src		src
storage		storage
tests		tests
.gitignore		.gitignore
LICENSE		LICENSE
README.md		README.md
composer.json		composer.json
phpunit.xml		phpunit.xml

Name		Name	Last commit message	Last commit date
.github/workflows		.github/workflows
config		config
src		src
storage		storage
tests		tests
.gitignore		.gitignore
LICENSE		LICENSE
README.md		README.md
composer.json		composer.json
phpunit.xml		phpunit.xml

Name		Name	Last commit message	Last commit date
.github/workflows		.github/workflows
config		config
src		src
storage		storage
tests		tests
.gitignore		.gitignore
LICENSE		LICENSE
README.md		README.md
composer.json		composer.json
phpunit.xml		phpunit.xml

Name		Name	Last commit message	Last commit date
.github/workflows		.github/workflows
config		config
src		src
storage		storage
tests		tests
.gitignore		.gitignore
LICENSE		LICENSE
README.md		README.md
composer.json		composer.json
phpunit.xml		phpunit.xml

Name		Name	Last commit message	Last commit date
.github/workflows		.github/workflows
config		config
src		src
storage		storage
tests		tests
.gitignore		.gitignore
LICENSE		LICENSE
README.md		README.md
composer.json		composer.json
phpunit.xml		phpunit.xml

Latest commit

History

Folders and files

Repository files navigation

Blade Script

Introduction

Installation

Include Scripts

Usage

Optimizing Scripts

Write Transpiler

About

Resources

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages

Latest commit

History

Folders and files

Repository files navigation

Blade Script

Introduction

Installation

Include Scripts

Usage

Optimizing Scripts

Write Transpiler

About

Resources

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages

Latest commit

History

Folders and files

Repository files navigation

Blade Script

Introduction

Installation

Include Scripts

Usage

Optimizing Scripts

Write Transpiler

About

Resources

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages

Latest commit

History

Folders and files

Repository files navigation

Blade Script

Introduction

Installation

Include Scripts

Usage

Optimizing Scripts

Write Transpiler

About

Resources

Stars

Watchers

Forks

Releases