Joomla! Issue Tracker | Joomla! CMS #42428 - [5.x] Localize own package

RTC NPM Resource Changed PR-5.1-dev

Fixed in Code Base
2 Mar 2024
Medium
Build: 5.0-dev
# 42428
Diff
dgrammatiko:5.0-dev-drop-package

Pending

User tests: Successful: Unsuccessful:

dgrammatiko
29 Nov 2023

Pull Request for Issue # .

Summary of Changes

Localise my own gzip package @dgrammatiko/compress

Testing Instructions

Check out this PR

run npm i
run npm gzip

Check that the gzipped files inside the media folder are created
Rename the htaccess.txt and check if the gzipped files are loading correctly

Actual result BEFORE applying this Pull Request

Expected result AFTER applying this Pull Request

Link to documentations

Please select:

Documentation link for docs.joomla.org:
No documentation changes for docs.joomla.org needed
Pull Request link for manual.joomla.org:
No documentation changes for manual.joomla.org needed

918bb2c 29 Nov 2023

Localize own package

dgrammatiko - open - 29 Nov 2023

dgrammatiko - change - 29 Nov 2023

Status

New

⇒

Pending

joomla-cms-bot - change - 29 Nov 2023

Category

⇒

JavaScript Repository NPM Change

MacJoom - alter_testresult - 5 Dec 2023 - MacJoom: Not tested

MacJoom - test_item - 5 Dec 2023 - Tested successfully

MacJoom - comment - 5 Dec 2023

I have tested this item ✅ successfully on 918bb2c

Gzip files are created. Website loads OK. I had to run 'composer install' after checkout. Then 'npm ci', then 'npm run gzip' (not npm gzip). Turned on 'Gzip Page Compression' in Global Configuration, Server Tab. Check Requests to js or css in Browser debug page. Content-Encoding must be gzip.

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/42428.}