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

State of Source Maps 2013 #531

Closed
paulirish opened this issue Aug 1, 2013 · 7 comments
Closed

State of Source Maps 2013 #531

paulirish opened this issue Aug 1, 2013 · 7 comments

Comments

@paulirish
Copy link
Member

author: @ryanseddon
doc: https://docs.google.com/a/google.com/document/d/1AQ5z4aZTtV0vo8gcnIO0OJFKduwZEkjTO_FPFf-uTEM/edit

@paullewis
Copy link
Contributor

Is there a way to make this agnostic in terms of time? I think it might be better to aim to cover source maps definitively.... it could just be a naming thing.

@ryanseddon
Copy link
Contributor

I'm easy on title change, as long as the nature of the article is still how far source maps have come and how it can integrated into your workflow.

@paullewis
Copy link
Contributor

I think that's great, I'm just keen to avoid anything that's too transient in what it describes. But certainly what you're saying in terms of being integrated to workflow, and essentially something a developer can (and should) use sounds perfect.

@paulirish
Copy link
Member Author

Adding @paulmillr to the article. he's going to add in some Brunch-y details, it sounds like.

@paulmillr
Copy link

Yup, pretty much.

@michaelficarra
Copy link

Add @michaelficarra?

@paulirish
Copy link
Member Author

np done.

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

No branches or pull requests

6 participants