Gathering detailed insights and metrics for @ckeditor/ckeditor5-vue2
Gathering detailed insights and metrics for @ckeditor/ckeditor5-vue2
Gathering detailed insights and metrics for @ckeditor/ckeditor5-vue2
Gathering detailed insights and metrics for @ckeditor/ckeditor5-vue2
npm install @ckeditor/ckeditor5-vue2
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
35 Stars
233 Commits
18 Forks
13 Watching
1 Branches
54 Contributors
Updated on 15 Nov 2024
JavaScript (98.63%)
Shell (1.37%)
Cumulative downloads
Total Downloads
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
30
⚠️ 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.
See the "Rich text editor component for Vue.js" guide in the CKEditor 5 documentation to learn more:
After cloning this repository, install necessary dependencies:
1npm install
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 to dots
).--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.
Build a minified version of the package that is ready to publish:
1npm run build
1npm run changelog
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.
Before starting the release process, you need to generate the changelog:
1npm run changelog
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.
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
Reason
license file detected
Details
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
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
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