-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[4.0] Kill grunt! #18446
The head ref may contain hidden characters: "\u00A74.0-dev-kill-grunt"
[4.0] Kill grunt! #18446
Conversation
I forgot to mention that: |
You appear to be loading the wrong jQuery UI package from NPM. Should be this: https://www.npmjs.com/package/jquery-ui |
Also, can we kill the uncompressed CSS files please? We're not using them at all. |
package.json
Outdated
{ | ||
"targets": { | ||
"browsers": [ | ||
"last 2 versions", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be last 1 version
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this one is for babel, not postcss
build/build-modules-js/update.js
Outdated
|
||
// Update the XML files for Codemirror | ||
let codemirrorXml = fs.readFileSync(rootPath + '/plugins/editors/codemirror/codemirror.xml', {encoding: 'UTF-8'}); | ||
codemirrorXml = codemirrorXml.replace(xmlVersionStr, "$1" + options.dependencies.tinymce + "$3"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
options.dependencies.tinymce
should be options.dependencies.codemirror
as you've reverted Codemirror back to 4.7.1 :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oops
Unless you're going to kill support for the core templates and core media loading uncompressed files in debug mode they should stay. |
@mbabker - Atum doesn't have any uncompressed CSS files and works perfectly fine in debug mode: https://github.com/joomla/joomla-cms/tree/4.0-dev/administrator/templates/atum/css |
I know it all works fine in debug mode. JHtml only uses uncompressed if it can take a This might be OK for the template media, but it should still be possible to get the core media in uncompressed format. Which means either we keep them in repo & ship them or people have to go through extra steps to compile them. |
@DGT41 it is still WIP? |
@DGT41 ignore me, all works fine |
@DGT41 one note:
I found it confusing, because you have And question.
|
@Fedik that's an interesting idea, I have to explore that |
Could we get the conflicts on this fixed please and then merge? Any improvements can be made at a later date |
Just recompile and remove the grunt-settings.yaml |
@wilsonge important please merge this!! |
@wilsonge please merge. This is a choice made by the JS team and will also assist the Ciaran and myself who are the primary people making use of the feature. |
@wilsonge any decision here, before you merge more things and make this harder to get it again in sync? |
Fix the conflicts and I'll merge it. I'm very uneasy about this to be honest. I still think gulp might be better for us. But let's just get it in so it's not blocking you guys |
This is in-sync again. Ping @wilsonge |
You need to fix travis please |
Travis is happy again |
Thank you! |
* [4.0] Remove grunt in favour of native node build scripts (joomla#18446) * These are junk * First pass on converting JS * Fix path to loader * CS tweaks for IFW JS, move event listener registration into success callback so that the changed DOM elements correctly receive them, change how custom events are triggered so they'll actually work * Make sure elements exist in DOM
We are in the process pf fixing things |
* [4.0] Remove grunt in favour of native node build scripts (#18446) * These are junk * First pass on converting JS * Fix path to loader * CS tweaks for IFW JS, move event listener registration into success callback so that the changed DOM elements correctly receive them, change how custom events are triggered so they'll actually work * Make sure elements exist in DOM
Pull Request for Issue # .
Summary of Changes
Two years ago (or so) I did this Grunt file with the aim to lift some of the day to day tasks for maintainers and also provide an easy way for contributors to compile scss files and minify js and css.
As the project (J4) moved on we added a lot more functionality and the file reached about 800 lines of code, which is kinda awkward for a task runner file.
Also we already encounter (a few times) that plugins will fall out of sync with the latest releases of the underlaying scripts (postfix, uglify, etc).
Therefore I propose a a better (for the long term) solution: plain node js code, no Grunt, no Gulp, no Webpack or Rollup. The tasks are pretty straight forward and we're not doing any packaging so webpack and rollup are totally out of the picture.
Also we are now using the package.json as the only point of truth (used to be another yaml file)
Available Commands
Expected result
Same functionality as Grunt (some command)
Documentation Changes Required
For documentation just run
or just
Enjoy!
Preview