
Research
/Security News
npm Package Uses Prompt Injection and Token Flooding to Disrupt AI Malware Scanners
A new npm package tests AI malware scanners with prompt injection, safety-triggering comments, context flooding, and obfuscated JavaScript.
@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}.bun 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 1,015 weekly downloads. As such, @ecopages/postcss-processor popularity was classified as 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.

Research
/Security News
A new npm package tests AI malware scanners with prompt injection, safety-triggering comments, context flooding, and obfuscated JavaScript.

Product
Socket now detects supply chain risks in project manifests, starting with missing lockfiles that can make dependency installs non-reproducible.

Research
/Security News
The trojanized extensions use TinyGo-compiled WebAssembly and Solana transaction memos to resolve command-and-control infrastructure.