
Security News
Another Round of TEA Protocol Spam Floods npm, But It’s Not a Worm
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.
yoast-components
Advanced tools
React components for use within different Yoast React projects.
You can install yoast-components using npm:
npm install yoast-components
import Input from 'yoast-components/forms/Input'
// Then you can use the Input component within your React components
If you use yoast-components within your own project we recommend using webpack with the following loaders and configuration:
Webpack 2+ configuration:
module.exports = {
// ...
module: {
rules: [
{
test: /\.jsx?$/,
exclude: /node_modules/,
use: [ {
loader: "babel-loader",
} ],
},
// ...
],
},
// ...
}
.babelrc:
{
"presets": ["es2015", "react"]
}
In the entry of your webpack you should include babel-polyfill as the very first element:
module.exports = {
// ...
entry: [
"babel-polyfill",
// ...
"your-app-entry.js"
]
// ...
}
Some components require implementing a reducer. See which components need what reducers below:
If you wish to use the content analysis component you should implement the contentAnalysisReducer, located in yoast-components/composites/Plugin/ContentAnalysis/reducers/contentAnalysisReducer.js. In your root reducer this reducer should have the name contentAnalysis.
import contentAnalysis from "yoast-components/composites/Plugin/ContentAnalysis/reducers/contentAnalysisReducer.js";
// Your root reducer
combineReducers( {
// ...
contentAnalysis: contentAnalysis,
// ...
} );
yarn install in the root folder.yarn start in the root folder.http://localhost:3333yarn test
To test the code style:
grunt check
Every component should have its own folder named lowercase with the relevant files inside of it. Every component must contain a JavaScript with the component definition in it and exported using export default [Component]. Any component can contain a SCSS file for relevant CSS and a README.md explaining how the component works.
We use i18n-calypso to localize all components. Refer to their documentation about how to use translate, moment and numberFormat. We don't use the mixin provided. Only use the higher order component to wrap components when they are exported, like so:
import { localize } from 'i18n-calypso'
export default localize( Component );
If you discover any security related issues, please email security [at] yoast.com instead of using the issue tracker.
We follow the GPL. Please see License file for more information.
wordpress-seo11. With some minor tweaks this can also be used to develop yoast-components within other projects
If you would like to develop yoast-components within the wordpress-seo plugin, you can do this quite easily using yarn.
yoast-components project to wordpress-seo using the command line:
yoast-components project run yarn link.wordpress-seo project run yarn link "yoast-components".Now you can make development easier by having grunt watch your files:
wordpress-seo open Gruntfile.js.project, add the following line to paths>files>js[]:
node_modules/yoast-components/**/*.jsgrunt watchFAQs
Yoast Generic Components
We found that yoast-components demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.

Security News
PyPI adds Trusted Publishing support for GitLab Self-Managed as adoption reaches 25% of uploads

Research
/Security News
A malicious Chrome extension posing as an Ethereum wallet steals seed phrases by encoding them into Sui transactions, enabling full wallet takeover.