Re: lavarel: compiled files

Path	csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From	Arno Welzel <usenet@arnowelzel.de>
Newsgroups	comp.lang.php
Subject	Re: lavarel: compiled files
Date	Thu, 26 May 2022 17:45:18 +0200
Lines	28
Message-ID	<jf9lkeFu8j6U1@mid.individual.net> (permalink)
References	<t6le7v$61v$1@gioia.aioe.org>
Mime-Version	1.0
Content-Type	text/plain; charset=UTF-8
Content-Transfer-Encoding	7bit
X-Trace	individual.net h3N5gVZEhfynPmsNvPOTAAQSmHSObjKFQRfCd0GSVx2tAZShbh
Cancel-Lock	sha1:yDZbifpEd/ceY4v1EqSa4BaiNYI=
Content-Language	de-DE
In-Reply-To	<t6le7v$61v$1@gioia.aioe.org>
Xref	csiph.com comp.lang.php:18946

Show key headers only | View raw

Fx ROOM:

> https://laravel.com/docs/9.x/structure#the-resources-directory
> The resources directory contains your views as well as your raw, 
> un-compiled assets such as CSS or JavaScript.
> 
> ????
> 
> Instead the files in the other directories are compiled?

Yes.

Usually for production JavaScript and CSS gets "compiled". This is not
the same as compiling source code to a binary form, but still the
"compiled" versions are optimized for production use.

Example:

<https://arnowelzel.de/res-3.4.2/wp-content/plugins/lightbox-photoswipe/assets/scripts.js>

This file is based on multiple "source" files which get combined and
"minified" for production use. This can also be seen als "compiling"
something.


-- 
Arno Welzel
https://arnowelzel.de

Thread

lavarel: compiled files Fx ROOM <naso@tata.new> - 2022-05-25 16:25 +0200
  Re: lavarel: compiled files Arno Welzel <usenet@arnowelzel.de> - 2022-05-26 17:45 +0200
    Re: lavarel: compiled files Fx ROOM <naso@tata.new> - 2022-05-27 11:09 +0200
      Re: lavarel: compiled files Arno Welzel <usenet@arnowelzel.de> - 2022-05-27 13:47 +0200

csiph-web