Tommy Dew

Found we can use `Writable` to capture the log! Will follow the [pattern](https://github.com/pinojs/pino-pretty/blob/68f22d4548297dcb83b7d675dd56c5f2cd5df7ac/test/basic.test.js#L54-L65) in `pino-pretty` to write unit tests.

Say we have this now: ```js fastify({ logger: { transport: 'one-line-logger' } }) ``` What unit tests should we include? Here are what I can think of/get from searching the...

Hi thanks for the explanation! If we still don't have this feature, I'm happy to work on it!

I can give it a try. The state has to go one level deeper than the usual: ```jsx // instead of usually the state is directly pass as a arg...

> I will fix this bug after [this pr](https://github.com/pynecone-io/pynecone/pull/571) is merged. Thank you so much!! Any chance we can have an unit test for this issue? If our change in...

Hey @d29107d! I'm just wondering if we can have a unit test for #490 i.e. the issue of the current webpage. Would be great if we can have one! Since...

I can also work on this. How would the feature look like in code? Sth like this?: ```py app = pc.App() app.add_page(index, custom_js_scripts=[js_code_str_1, js_code_str_2]) ```

Interestingly we have already had a [pc.script](https://github.com/pynecone-io/pynecone/blob/f22c67e48c9156ae0616611e3561f8b97fe8bb56/pynecone/components/base/document.py#L30-L33). It looks to me it's a nextjs [NextScript](https://nextjs.org/docs/basic-features/script) object.

I'll suggest we rename the [pc.script](https://github.com/pynecone-io/pynecone/blob/f22c67e48c9156ae0616611e3561f8b97fe8bb56/pynecone/components/base/document.py#L30-L33) to `NextScript` instead. I think this component is only used internally in the framework so it's probably fine. And create a `Script` component.

@gringrape i guess add one more component `ScriptTag` to the codebase. Then we can render that component to the page. So the whole feature would be sth like this?: ```py...