-
Notifications
You must be signed in to change notification settings - Fork 12
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
Deploy for Node.js #87
Comments
There's been progress recently on this, when we worked on the new builder (pending documentation). We can do now this:
So close... :D But it only requires now that we transpile ES6 features which Node.JS does not support yet, or upgrade Node and we're home. The code loads and works unless it depends on DOM, so we'll need to remove these dependencies to make it fully functional. |
Related page in the wiki: https://github.com/ckeditor/ckeditor5-design/wiki/Modularity |
I am working on a task that will enable running our tests in Node.js environment.
At the moment all above is nearly done, I am currently writing tests for the new functionalities. After that PR will be ready for review. |
Status update – we had a deploy for Node working and tested for some time, but since we're not using it it got abandoned. However, the architecture was aligned to this requirement so there's no problem in initializing headless and viewless editors in Node.js and we had confirmation that it works fine. Of course, to load the code in Node.js you need to first transpile ES6 modules to CSJ modules. I hope that it may soon be resolved by the adoption of ES6 modules by Node.js. |
I propose to make distributions targeting Node.js. This is related to #86, which involves the ability to create headless editors. In this way one could benefit from the CKEditor API on the server side as well.
The text was updated successfully, but these errors were encountered: