
Product
Introducing Webhook Events for Alert Changes
Add real-time Socket webhook events to your workflows to automatically receive software supply chain alert changes in real time.
postcss-anywhere-import
Advanced tools
PostCSS plugin to import CSS files (anywhere from top to bottom of a CSS file)
PostCSS plugin to transform
@importrules by inlining content.
This plugin can consume local files, node modules or web_modules.
To resolve path of an @import rule, it can look into root directory (by default process.cwd()), web_modules, node_modules or local modules.
When importing a module, it will look for index.css or file referenced in package.json in the style or main fields.
You can also provide manually multiples paths where to look at.
Notes:
url() (or even inline them) after inlining imported files.skipDuplicates optiondataUrls plugin option to extend postcss-import.options.filter or because they are remote imports) are moved to the top of the output.@import spec; @import statements must precede all other statements (besides @charset).$ npm install -D postcss-anywhere-import
Unless your stylesheet is in the same place where you run postcss
(process.cwd()), you will need to use from option to make relative imports
work.
// dependencies
const fs = require("fs")
const postcss = require("postcss")
const atImport = require("postcss-anywhere-import")
// css to be processed
const css = fs.readFileSync("css/input.css", "utf8")
// process css
postcss()
.use(atImport())
.process(css, {
// `from` option is needed here
from: "css/input.css"
})
.then((result) => {
const output = result.css
console.log(output)
})
css/input.css:
/* remote urls are preserved */
@import "https://example.com/styles.css";
/* can consume `node_modules`, `web_modules` or local modules */
@import "cssrecipes-defaults"; /* == @import "../node_modules/cssrecipes-defaults/index.css"; */
@import "normalize.css"; /* == @import "../node_modules/normalize.css/normalize.css"; */
@import "foo.css"; /* relative to css/ according to `from` option above */
body {
background: black;
}
/* all standard notations of the "url" value are supported */
@import url(foo-1.css);
@import url("foo-2.css");
@import "bar.css" (min-width: 25em);
@import 'baz.css' layer(baz-layer);
will give you:
@import "https://example.com/styles.css";
/* ... content of ../node_modules/cssrecipes-defaults/index.css */
/* ... content of ../node_modules/normalize.css/normalize.css */
/* ... content of css/foo.css */
body {
background: black;
}
/* ... content of css/foo-1.css */
/* ... content of css/foo-2.css */
@media (min-width: 25em) {
/* ... content of css/bar.css */
}
@layer baz-layer {
/* ... content of css/baz.css */
}
Checkout the tests for more examples.
anywhereImportType: Boolean
Default: true
Allow this PostCSS plugin to consider any @import mentions and using anywhere/anyplace
inside your .css files. If you want to regret to default version of this plugin
like postcss-import turn this anywhereImport
option to false.
filterType: Function
Default: () => true
Only transform imports for which the test function returns true. Imports for
which the test function returns false will be left as is. The function gets
the path to import as an argument and should return a boolean.
rootType: String
Default: process.cwd() or dirname of
the postcss from
Define the root where to resolve path (eg: place where node_modules are).
Should not be used that much.
Note: nested @import will additionally benefit of the relative dirname of
imported files.
pathType: String|Array
Default: []
A string or an array of paths in where to look for files.
pluginsType: Array
Default: undefined
An array of plugins to be applied on each imported files.
resolveType: Function
Default: null
You can provide a custom path resolver with this option. This function gets
(id, basedir, importOptions) arguments and should return a path, an array of
paths or a promise resolving to the path(s). If you do not return an absolute
path, your path will be resolved to an absolute path using the default
resolver.
You can use resolve for this.
loadType: Function
Default: null
You can overwrite the default loading way by setting this option.
This function gets (filename, importOptions) arguments and returns content or
promised content.
skipDuplicatesType: Boolean
Default: true
By default, similar files (based on the same content) are being skipped.
It's to optimize output and skip similar files like normalize.css for example.
If this behavior is not what you want, just set this option to false to
disable it.
addModulesDirectoriesType: Array
Default: []
An array of folder names to add to Node's resolver.
Values will be appended to the default resolve directories:
["node_modules", "web_modules"].
This option is only for adding additional directories to default resolver. If
you provide your own resolver via the resolve configuration option above, then
this value will be ignored.
nameLayerType: Function
Default: null
You can provide a custom naming function for anonymous layers (@import 'baz.css' layer;).
This function gets (index, rootFilename) arguments and should return a unique string.
This option only influences imports without a layer name. Without this option the plugin will warn on anonymous layers.
const postcss = require("postcss")
const atImport = require("postcss-anywhere-import")
postcss()
.use(atImport({
path: ["src/css"],
}))
.process(cssString)
.then((result) => {
const { css } = result
})
dependency Message Supportpostcss-anywhere-import adds a message to result.messages for each @import. Messages are in the following format:
{
type: 'dependency',
file: absoluteFilePath,
parent: fileContainingTheImport
}
This is mainly for use by postcss runners that implement file watching.
$ npm test).FAQs
PostCSS plugin to import CSS files (anywhere from top to bottom of a CSS file)
We found that postcss-anywhere-import demonstrated a not healthy version release cadence and project activity because the last version was released 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.

Product
Add real-time Socket webhook events to your workflows to automatically receive software supply chain alert changes in real time.

Security News
ENISA has become a CVE Program Root, giving the EU a central authority for coordinating vulnerability reporting, disclosure, and cross-border response.

Product
Socket now scans OpenVSX extensions, giving teams early detection of risky behaviors, hidden capabilities, and supply chain threats in developer tools.