Re: lavarel: compiled files

From	Arno Welzel <usenet@arnowelzel.de>
Newsgroups	comp.lang.php
Subject	Re: lavarel: compiled files
Date	2022-05-27 13:47 +0200
Message-ID	<jfbs1jFcgsgU1@mid.individual.net> (permalink)
References	<t6le7v$61v$1@gioia.aioe.org> <jf9lkeFu8j6U1@mid.individual.net> <t6q4ga$uin$2@gioia.aioe.org>

Show all headers | View raw

Fx ROOM:

> Il 26/05/22 17:45, Arno Welzel ha scritto:
>> 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.
> 
> thanks

In addition - also see LESS and SASS which also "compile" CSS:

<https://css-tricks.com/sass-vs-less/>

And you should also know about Webpack:

<https://webpack.js.org>

I don't know how Laravel handles this, but in Symfony based projects the
preferred way to deal with frontend assets is Webpack Encore:

<https://www.npmjs.com/package/@symfony/webpack-encore>


-- 
Arno Welzel
https://arnowelzel.de

Back to comp.lang.php | Previous | Next — Previous in thread | Find similar | Unroll thread

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