Skip to content
This repository has been archived by the owner on Dec 19, 2024. It is now read-only.

write to a separate source map file from CLI #107

Closed
jonathanong opened this issue Apr 29, 2015 · 7 comments · Fixed by #238
Closed

write to a separate source map file from CLI #107

jonathanong opened this issue Apr 29, 2015 · 7 comments · Fixed by #238

Comments

@jonathanong
Copy link

right now, you can only inline source maps. any way to allow separate source map files?

@MoOx
Copy link
Owner

MoOx commented Apr 29, 2015

@jonathanong
Copy link
Author

sorry. needed to be more specific. i'm currently trying via CLI w/ the watcher. trying to avoid a custom node.js script :)

@MoOx
Copy link
Owner

MoOx commented Apr 29, 2015

Hum so I think I've done nothing yet. Maybe we should handle #73 to allow options from json ?

@MoOx
Copy link
Owner

MoOx commented Apr 29, 2015

Maybe you can check if --config can help you (you can provide a .js config)...
Hum it seems -map option doesn't exist yet. Should not be that hard to add around here https://github.com/cssnext/cssnext/blob/62aeafb32a8d8f50a655152486bad0bac65e25b4/bin/cssnext.js#L72
PRs are welcome :)

@MoOx MoOx changed the title write to a separate source map file write to a separate source map file from CLI Apr 29, 2015
@jonathanong
Copy link
Author

yeah was looking into the config. i can add .map option to the config, but the source map is still not saved because it needs to be handled by the CLI.

how would you want the option to look like? --map [filename]? where filename is optional, and if it does not exist, inline like normally?

@MoOx
Copy link
Owner

MoOx commented Apr 29, 2015

--sourcemap is already inlining normally, so I guess if you use --map you must provide a filename. But yeah we can do that :) That should enable as well map entry in config file from wat I see in the code (I did not create the --config option).

@MoOx MoOx mentioned this issue Dec 29, 2015
5 tasks
@MoOx MoOx closed this as completed in #238 Jan 4, 2016
@MoOx
Copy link
Owner

MoOx commented Jan 4, 2016

Not relevant anymore. cssnext is now postcss-cssnext. cssnext is deprecated. See postcss-cssnext migration guide http://cssnext.io/postcss/

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants