Error: The "fileName" or "name" properties of emitted files must be strings that are neither absolute nor relative paths and do not contain invalid characters
See original GitHub issueI’m getting an error when I try to define a filename for the extract option.
postcss({
extract: 'dist/test.css',
…
})
v2.4.0:
[!] (plugin postcss) Error: The “fileName” or “name” properties of emitted files must be strings that are neither absolute nor relative paths and do not contain invalid characters, received “…/test.css”.
Works on v2.3.0.
Issue Analytics
- State:
- Created 4 years ago
- Comments:40 (3 by maintainers)
Top Results From Across the Web
rollup - How can I write CSS outside the JS destination folder
Error : The "fileName" or "name" properties of emitted files must be strings that are neither absolute nor relative paths and do not...
Read more >Impossible to extract CSS in a parent folder #265 - Issuehunt
The "fileName" or "name" properties of emitted files must be strings that are neither absolute nor relative paths and do not contain invalid...
Read more >TSConfig Reference - Docs on every TSConfig option
All relative paths found in the configuration file will be resolved relative to the configuration file they originated in. It's worth noting that...
Read more >VS Code API | Visual Studio Code Extension API
VS Code API is a set of JavaScript APIs that you can invoke in your Visual Studio Code extension. This page lists all...
Read more >GNU make
Searching other directories for source files. • Phony Targets, Using a target that is not a real file's name. • Force Targets, You...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It has not been fix this issue for 100 years
This comment by @lukastaegert provides the full solution. What I had to do was:
This works perfectly.