Download the PHP package jacerider/neo_build without Composer

On this page you can find all versions of the php package jacerider/neo_build. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of jacerider/neo_build

Informations about the package neo_build

CONTENTS OF THIS FILE

INTRODUCTION

Vite integration for Drupal asset libraries.

REQUIREMENTS

This module requires no modules outside of Drupal core.

It's designed to work with Vite 3 or newer and Tailwind and Typescript.

INSTALLATION

Install as you would normally install a contributed Drupal module. Visit https://www.drupal.org/node/1897420 for further information.

Add to .gitignore:

If using DDEV, create a file called neo.conf in .ddev/nginx/ with the following content:

USAGE

BUILD FOR DEV

To use hot module reload during development, run:

The server will run in non-HTTPS mode to avoid XSS issues. If the server is accessible on the localhost under default port (5173) the module will automatically start using it instead of dist assets from manifest.json as soon as you clear the cache (library definitions are cached by default).

BUILD FOR PROD

To compile js and css for all scopes (only 'contrib' group), run:

BUILD SCOPES

In <theme/module>.libraries.yml there is also an option to set the build scope. The scope impacts Tailwind so that aggregated classes are only built for the build of this scope when calling @tailwind base; within a CSS or SCSS file. For example:

A theme should define their supported scopes in their info.yml.

or

If a scope is not defined, theme will act on all scopes.

BUILD GROUPS

In <theme/module>.libraries.yml there is also an option to set the build group. The group controls what libraries are proccessed during dev. If no group is specified for a library, custom is used by default. By default, there are only two groups; 'custom' and 'contrib'. For example:

The contrib group should be used for contrib modules or themes.

SCSS GLOBAL INCLUDES

Sass stylesheets can be exposed so they can be loaded in other stylesheets using the @use rule.

To use includes within a Sass stylesheet:

CONFIGURATION

In library definition instead of only enabling neo support by setting neo: true theres also an option to provide some custom configurations.

These settings can also be overwritten in site settings.php:

In <theme/module>.libraries.yml there is also an option to disable rewriting of specific asset, to do that you need to set neo: false for specific asset. For example:

COMPONENTS

You can register new Tailwind components by defining them in your theme/module info file. For example:

THEME

You can extend the Tailwind base configuration by defining the settings in your theme/module info file. For example:

All versions of neo_build with dependencies

PHP Build Version
Package Version
Requires drupal/core Version ^10.3
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package jacerider/neo_build contains the following files

Loading the files please wait ....