Installations
npm install @ckeditor/ckeditor5-vue2
Developer
ckeditor
Developer Guide
Module System
CommonJS
Min. Node Version
>=14.0.0
Typescript Support
No
Node Version
14.19.1
NPM Version
8.5.5
Statistics
35 Stars
233 Commits
18 Forks
13 Watching
1 Branches
54 Contributors
Updated on 15 Nov 2024
Languages
JavaScript (98.63%)
Shell (1.37%)
Total Downloads
Cumulative downloads
Total Downloads
2,568,277
Last day
1.9%
2,931
Compared to previous day
Last week
0.5%
15,244
Compared to previous week
Last month
7.8%
67,763
Compared to previous month
Last year
-1.6%
804,770
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dev Dependencies
30
CKEditor 5 rich text editor component for Vue.js 2.x
⚠️ This repository contains the CKEditor 5 component for Vue.js 2.x
. The component for Vue.js 3+
is located in another repository - @ckeditor/ckeditor5-vue.
Official CKEditor 5 rich text editor component for Vue.js.
Developer Documentation 📖
See the "Rich text editor component for Vue.js" guide in the CKEditor 5 documentation to learn more:
- Quick start
- Using component locally
- Using CKEditor from source
- Using the Document editor build
- Component directives
- Component events
Contributing
After cloning this repository, install necessary dependencies:
1npm install
Executing tests
1npm run test -- [additional options] 2# or 3npm t -- [additional options]
The command accepts the following options:
--coverage
(-c
) – Whether to generate the code coverage.--source-map
(-s
) – Whether to attach the source maps.--watch
(-w
) – Whether to watch test files.--reporter
(-r
) – Reporter for Karma (default:mocha
, can be changed todots
).--browsers
(-b
) – Browsers that will be used to run tests (default:Chrome
, available:Firefox
).
If you are going to change the component (src/ckeditor.js
) or plugin (src/plugin.js
) files, remember about rebuilding the package. You can use npm run develop
in order to do it automatically.
Building the package
Build a minified version of the package that is ready to publish:
1npm run build
Changelog generator
1npm run changelog
Testing component with Vue CLI
When symlinking the component in an application generated using Vue CLI, make sure your vue.config.js
file configures webpack in the following way:
1module.exports = { 2 configureWebpack: { 3 resolve: { 4 symlinks: false 5 } 6 } 7};
Otherwise, the application will fail to load the component correctly and, as a result, it will throw a build error.
Releasing package
Changelog
Before starting the release process, you need to generate the changelog:
1npm run changelog
Publishing
After generating the changelog, you are able to release the package.
First, you need to bump the version:
1npm run release:prepare-packages
After bumping the version, you can publish the changes:
1npm run release:publish-packages
Note: The release/
directory will be published.
License
Licensed under the terms of GNU General Public License Version 2 or later. For full details about the license, please check the LICENSE.md file.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
security policy file detected
Details
- Info: security policy file detected: SECURITY.md:1
- Info: Found linked content: SECURITY.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
- Info: Found text in security policy: SECURITY.md:1
Reason
license file detected
Details
- Info: project has a license file: LICENSE.md:0
- Warn: project license file does not contain an FSF or OSI license.
Reason
8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
Reason
Found 4/7 approved changesets -- score normalized to 5
Reason
6 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-pxg6-pf52-xh8x
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-p8p7-x288-28g6
- Warn: Project is vulnerable to: GHSA-72xf-g2v4-qvf3
- Warn: Project is vulnerable to: GHSA-5j4c-8p2g-v4jx
- Warn: Project is vulnerable to: GHSA-g3ch-rx76-35fx
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 28 are checked with a SAST tool
Score
4.5
/10
Last Scanned on 2024-11-25
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More