csstools / csstools/postcss-normalize
postcss-import config missing options
- Langage dominant
- CSS
- Étoiles
- 837
- Forks
- 40
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
In the config object of `postcss-import`, there's a **path** option to define where it has to search for a file.
at the moment the only way is to create a resolve function:
```js
const path = require('path');
const atImport = require('postcss-import');
const postcssNormalize = require('postcss-normalize');
module.exports = {
// [...]
plugins: [
atImport(postcssNormalize(/* opts */).postcssImport({
resolve: (id) => path.resolve(__dirname, 'path/to/css', `${id}.css`),
})),
],
};
```
but we could be allowed to use **options.path**
```js
const atImport = require('postcss-import');
const postcssNormalize = require('postcss-normalize');
module.exports = {
// [...]
plugins: [
atImport(postcssNormalize(/* opts */).postcssImport({
path: 'path/to/css',
})),
],
};
```
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Search the repository for postcss-import configuration handling and related tests, then start at the entry point that passes options to the plugin. Use the issue examples to determine the expected path behavior. Done means options.path works without a custom resolve function and the relevant tests pass.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- css, javascript
- Domaine
- tooling
- Type d'issue
- Fonctionnalité
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 45/100