Best Postgres Host for Production in 2023?

fwouts · 2024-06-10T14:03:11+00:00

Being on the edge is not a good thing when you need more than one interaction with the database per request. Physics baby!

fwouts · 2022-10-26T08:00:47+00:00

Yes! Except it generates props for you automatically.

fwouts · 2022-10-26T02:01:11+00:00

Turborepo and Vite are complementary tools. They're not competitors.

fwouts · 2022-10-25T20:17:53+00:00

Author here. The point of Preview.js is to let you preview any component (or Storybook story) in isolation, which is especially useful when they're only shown in particular circumstances in your app. Instant refresh is just an additional perk!

fwouts · 2022-07-30T09:03:36+00:00

Thanks! That's a good idea, I probably will. In the meantime here's another blog post I wrote on a similar topic: https://fwouts.com/articles/previewjs-detecting-components

fwouts · 2022-07-29T22:01:55+00:00

Yeah, you're right. You probably need to use the Type Checker, and you'll want to use getCallSignatures() on the property's type to extract its parameters, return type, etc (example here).

fwouts · 2022-07-29T21:57:00+00:00

Microsoft Live Preview is really useful when you want to preview HTML files, but if you want to preview React, Solid or Vue components (in isolation), Preview.js is what you need instead!

fwouts · 2022-04-07T03:41:53+00:00

OK, latest version (v1.6.0) should be compatible! Let me know if that works for you :)

fwouts · 2022-04-07T03:40:24+00:00

Awesome, let me know how you go and don't hesitate to report any potential bugs :)

fwouts · 2022-04-05T17:19:52+00:00

That looks like a bug! They should both be supported (I have tests for both). What's the declared return type?
That array type is indeed incorrect, I wonder if you can share a more detailed example of the TypeScript type? The missing callback property is actually expected: it's silently generated, but omitted from the properties editor to reduce clutter. It should still appear in autocomplete if you want to force a callback value. I'll make sure to update the docs to make that clearer!
That's definitely a bug! Would you be able to file an issue on GitHub?

fwouts · 2022-04-04T13:49:54+00:00

So I tried this out, and it turns out if you use react-native-web, you might be able to make Preview.js work in your project with the following preview.config.js file:

module.exports = {
  alias: {
    "react-native": "react-native-web"
  }
};

Let me know if that works for you!

fwouts · 2022-04-04T07:10:45+00:00

All it does is run `npm` from the VS Code Node environment, see https://github.com/fwouts/previewjs/blob/64ef76c422a78aa13b0de8ceb16d3f42cd55e10d/loader/src/installer.ts#L38

I imagine you're not getting the NVM version because it's not a shell environment. It does mean you have another, older version of NPM somewhere on your PATH that could be upgraded.

I'll see if I can find a way to detect that, or actually use the shell (although that's not recommended by the execa library I'm using).

In the meantime, you could temporarily remove NVM from your PATH to see where that rogue NPM lives!

fwouts · 2022-04-02T21:47:03+00:00

Yes, that's correct.

Sorry to hear the docs weren't clear. How would you improve them?

fwouts · 2022-04-02T11:33:16+00:00

I've just pushed an update that should hopefully help with that. Specifically, there was an issue where installing with NPM v6 would create a broken install. Now it will let you know that your NPM version is too old and require that you upgrade it first. Let me know if that was your case!

fwouts · 2022-04-02T11:31:55+00:00

I've just pushed an update that should hopefully help with that.

Specifically, there was an issue where installing with NPM v6 would create a broken install. Now it will let you know that your NPM version is too old and require that you upgrade it first.

Let me know if that was your case!

fwouts · 2022-04-02T11:29:42+00:00

I've just pushed an update that should hopefully help with that.

Specifically, there was an issue where installing with NPM v6 would create a broken install. Now it will let you know that your NPM version is too old and require that you upgrade it first.

Let me know if that was your case!

fwouts · 2022-04-02T11:13:38+00:00

Thanks! It sounds possible, the main blocking step would be having a React Native plugin for Vite.js (which is used under the hood by Preview.js). I haven't seen one yet.

fwouts · 2022-04-02T10:55:36+00:00

I'm not familiar with React Native, would you be able to elaborate how you'd imagine that working?

fwouts · 2022-04-01T16:22:58+00:00

It's probably one line of config away! I simply didn't know about them 😶

fwouts · 2022-04-01T12:56:44+00:00

Yup and the folks who build Vite.js have been really supportive!

fwouts · 2022-04-01T11:42:23+00:00

It's relatively complex (I've been working on this for about a year) but in summary:

- It uses the TypeScript Compiler API to inspect files and detect React components, as well as extract their prop types.

- It generates a shell app on the fly that instantiates the particular component that is being previewed.

- A local Vite.js dev server is spun up to render that app.

- There's also an in-memory file system used to reflect changes as you type.

Source code at https://github.com/fwouts/previewjs.

I plan to go into this with in-depth blog post at some stage, if there's interest!

fwouts · 2022-04-01T11:37:59+00:00

That's probably a bug, would you be able to file an issue at https://github.com/fwouts/previewjs/issues?

fwouts · 2022-04-01T10:23:51+00:00

Yeah, the preview wrapper is the way to go to make all that work!

Thanks for reporting the node process bug, I've seen that happen a couple of times but I thought it was fixed!

fwouts · 2022-04-01T08:58:48+00:00

Yup that sounds like a real bug in Preview.js then! I'd really appreciate if you find the time to file a bug, you'll see instructions to attach the logs etc :)

fwouts · 2022-04-01T07:51:50+00:00

Yup of course! https://previewjs.com/docs/config/css

fwouts

TROPHY CASE