Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Making sense of the log. #299

Open
HaoZeke opened this issue Dec 3, 2017 · 5 comments
Open

Making sense of the log. #299

HaoZeke opened this issue Dec 3, 2017 · 5 comments

Comments

@HaoZeke
Copy link

HaoZeke commented Dec 3, 2017

I'm unable to understand the output of even specialized log plug-ins like metalsmith-logger.

I seem to end up with multiple [object Object] files in which I can't seem to resolve..

How does one figure out what data is being passed internally?

GraphQL does this part really well...

@Ajedi32
Copy link
Member

Ajedi32 commented Dec 8, 2017

I'm not quite sure what you're asking. Can you post a MCVE of the problem you're experiencing?

@Zearin
Copy link
Contributor

Zearin commented Jun 4, 2018

@HaoZeke I have been in your exact situation. I am unhappy with Metalsmith’s logging situation, and I hope to do something about it in v3.0.

But something that is helpful right now is metalsmith-debug-ui. It’s pretty minimalist, but it does something amazing (and useful!):

It takes a snapshot of the entire files object between each plugin, allowing you to look at any stage of the transformation process. I’ve found it incredibly useful in my own projects.

Give it a try, and let me know how it goes!

@HaoZeke
Copy link
Author

HaoZeke commented Jun 4, 2018

@Zearin unfortunately I was using gulp-metalsmith so the debug ui wasn't working for me..

I really hope metalsmith has better logging in the next release.

@Zearin
Copy link
Contributor

Zearin commented Jun 4, 2018

Can you try going without gulp-metalsmith just long enough to use metalsmith-debug-ui and determine the problem? You can always figure it out and then go back to your normal setup afterwards....

@HaoZeke
Copy link
Author

HaoZeke commented Jun 4, 2018

Yup, I had taken some time off, I'll be checking it out soon.

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

No branches or pull requests

3 participants