-
Notifications
You must be signed in to change notification settings - Fork 413
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
Provide compiled but non-minimized resources (JS/CSS) #11
Comments
You can easily build CKEditor without minifying source using https://github.com/ckeditor/ckeditor-presets or the builder in https://github.com/ckeditor/ckeditor-dev passing So, none of the currently available options is perfect, but I think that they are "convenient enough" :). Adding unminified versions of releases would lengthen the release process which already takes some time. But, let's see. I'm not closing this issue, so if more developers will be interested in such repo/branches, then we can consider it. |
Hmm I believe that source maps would be the best option... but it might be troublesome to provide them for packages created with online builder as it operates on a number of precompiled files and then merges them into one and adds some additional things. As for the rest, I agree with Piotrek. If we see more interested users in this topic, we'll take a look into it. |
I just ran into some issues with CKEditor, and I have to agree that it would be very nice to have an unminified version to work with. As it stands I'll have to follow @Reinmar's advice and hope for the best, although I anticipate it will be a pain to get the build config "just so". My vote it to add and unminified build to these releases. |
+1 on providing unminified css/js I've narrowed a bundling problem with ckeditor run-time error JS1019: Can't have 'break' outside of loop: break a commenting out ckeditor.js - bundling works correctly. {name}.js |
When it comes to source maps, I'm affraid I have some bad news. I already shared my concerns about producing source maps using online builder. Today I have to add that also adding source maps support inside command line builder is not that easy due to the way that we create minified files. Basically CKBuilder:
As you see, with the current release process it's quite troublesome to provide a sourcemap that would provide an information about from which files the minified code is coming. What we can (relatively) easily do is to provide a source map without any information about source files, but... that would be almost the same as using version created with the |
So how come when I use the Builder and I check the "Source (Big 'n' Slow)" checkbox, my downloaded ckeditor.js is still minified? I am encountering a bug that will be easy to fix once I have the non-minified source - the fix will take maybe 10-15 minutes. But because the verbiage on the Builder page is misleading (what am I getting that I wouldn't be getting if I download an optimized build? Either way, ckeditor.js is minified and the plugins are unminified... I see no difference between the two. I suppose I'll go check out the source from Github and build it, but I have already wasted time that I don't have, and now I'm wasting more, because I tried a build option that apparently doesn't do anything differently. |
Hm. I'm going to dive into the source on Github, but I'm also wondering if there's a provision to build CKEditor on a Windows machine.... although I think I have MSYS installed, so running build.sh may actually be possible... |
Apologies for the multiple posts. Is it possible to get a STABLE unminified copy of CKEditor somehow? I am not about to use an alpha version on a production website. 4.4.6 is working fine with the exception of one bug that I need to patch. |
As mentioned in an earlier comment:
In short: Step 1:
(make sure to change the version number for the latest stable version, in case of versions earlier than 4.8.0 you may need to adjust Step 2: To build release version (minified)
OR To build release version (with JavaScript files concatenated in correct order, but uncompressed)
|
Switch the order. First you should check the branch out, then you can update submodules. |
As this is a few years old - is it possible to provide source maps with the minified code or is this still an issue - I agree using the unminified version is doable but surely as source maps are a lot easier to generate now in a JS build pipeline surely this can easily be provided as part of the download - thanks |
@MarkAPhillips unfortunately CKBuilder doesn't produce source maps 😞 So the only way to debug is to build it with js files unminified as mentioned above. |
Same issue here and option |
I added that parameter to |
Why not switch to an alternative build process such as webpack? source maps are fairly important to have. |
If you need webpack support check CKEditor 5. |
I tried the commands wwalc suggested on 2014-12-29, and this failed (on 2 machines on 2 tested) at the fourth command:
So, to answer Reinmar's question, I do think adding unminified builds would be worth it. I don't know how much time that would add to releases, but I have 10+ years of web development experience, I have been trying to get a clean CKEditor source for 2 hours now, and I still haven't succeeded. And it's the second time I have to debug a problem with our WYSIWYG editor and things are complicated by lack of source. |
@Chealer before 2017 (version 4.8.0) the submodules in If you call:
it will work. Alternatively if you want to checkout some very old version of CKEditor then you need to correct manually the |
Thank you wwalc, I managed to complete step 1 for CKEditor 4.5.6 by editing .gitmodules. I also managed to complete the whole procedure. However, the result was missing plugins until I went back to step 2 and modified the command to So, to recap:
For versions prior to 4.8.0, edit .gitmodules per the above comment. This will result in an unminified equivalent to a CKEditor version profile in ckeditor-presets/build/version/profile/ckeditor/. |
Hey guys,
you are doing great job with providing CKEditor as Bower package.
One thing that I would appreciate is having access to compiled (released) version of CKEditor 4 but without doing minification/uglification/obfuscation.
I'm not sure whether it is achieavable in current CKEditor build system,
but the problem with obfuscated resources is that they can't be easily debugged (when source maps aren't provided)
On the other hand, you can't simply switch released repo (
ckeditor
bower dependency) to dev repo (ckeditor-dev
bower dependency) to debug.Do you consider it a valid issue?
Should I report this issue to CKEditor issue tracker?
The text was updated successfully, but these errors were encountered: