
Security News
npm v12 Ships With Install Scripts Off by Default, Begins Deprecating 2FA-Bypass Tokens
npm v12 is generally available, turning install scripts off by default and beginning the deprecation of 2FA-bypass publishing tokens.
@ecopages/postcss-processor
Advanced tools
PostCSS processing pipeline for Ecopages. It provides a processor plugin that seamlessly integrates PostCSS into the Ecopages build system, and includes built-in presets for Tailwind CSS (v3 and v4).
postcss.config.{js,ts,etc}.bunx jsr add @ecopages/postcss-processor
Integrate the processor into your eco.config.ts using a preset.
Requires @tailwindcss/postcss and tailwindcss to be installed.
// eco.config.ts
import path from 'node:path';
import { ConfigBuilder } from '@ecopages/core/config-builder';
import { postcssProcessorPlugin } from '@ecopages/postcss-processor';
import { tailwindV4Preset } from '@ecopages/postcss-processor/presets/tailwind-v4';
const config = await new ConfigBuilder()
.setProcessors([
postcssProcessorPlugin(
tailwindV4Preset({
referencePath: path.resolve(import.meta.dirname, 'src/styles/app.css'),
}),
),
])
.build();
export default config;
Requires tailwindcss@3, autoprefixer, postcss-import, and cssnano to be installed.
// eco.config.ts
import { ConfigBuilder } from '@ecopages/core/config-builder';
import { postcssProcessorPlugin } from '@ecopages/postcss-processor';
import { tailwindV3Preset } from '@ecopages/postcss-processor/presets/tailwind-v3';
const config = await new ConfigBuilder().setProcessors([postcssProcessorPlugin(tailwindV3Preset())]).build();
export default config;
To use your own postcss.config.js, simply call postcssProcessorPlugin() without arguments.
You can also pass raw plugins or transformation hooks manually:
import { ConfigBuilder } from '@ecopages/core/config-builder';
import { postcssProcessorPlugin } from '@ecopages/postcss-processor';
import myPlugin from 'postcss-my-plugin';
const config = await new ConfigBuilder()
.setProcessors([
postcssProcessorPlugin({
filter: /\.css$/,
plugins: {
'my-plugin': myPlugin(),
},
transformInput: async (css) => `/* Header */\n${css}`,
transformOutput: async (css) => css.replace('blue', 'red'),
}),
])
.build();
export default config;
You can bypass Ecopages entirely and use the processor utilities directly:
import { PostCssProcessor } from '@ecopages/postcss-processor';
// Process a file
const css = await PostCssProcessor.processPath('path/to/file.css');
// Process a string
const result = await PostCssProcessor.processStringOrBuffer('.class { @apply bg-red-500; }', { filePath: 'style.css' });
FAQs
Postcss processor, transform string or postcss file to css
The npm package @ecopages/postcss-processor receives a total of 421 weekly downloads. As such, @ecopages/postcss-processor popularity was classified as not popular.
We found that @ecopages/postcss-processor demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer 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
npm v12 is generally available, turning install scripts off by default and beginning the deprecation of 2FA-bypass publishing tokens.

Research
/Security News
Socket tracks the activity as Operation “Muck and Load”: a threat actor uses commit-farming workflows, public dead drops, and protected archives to stage Windows RAT and infostealer malware.

Security News
pnpm 11.10 hardens registry auth to block token redirection, tightens pack-app and deploy, and makes the Rust port (v12) installable.