How to setup a root bsconfig for rewatch?
Thanks, that does help a little, though I think there’s a step missing as I’m getting this error: [1/7]📦 Building package tree...[1/2] ️🛑 Error building package tree. The package "@app/client" is not...
View ArticleHow to setup a root bsconfig for rewatch?
it works fine for me with pnpm workspaces instead of bsconfig.json I use rescript.json { "name": "ventas", "sources": [ { "dir": "src/components", "subdirs": false }, { "dir": "tests", "subdirs":...
View Article[feature-recuest] VSCode extension: show available variables within scope of...
You know when using Chrome debugger that you set a breakpoint and you see all the available data within that scope. It would be helpful to have something similar in ReScript’s VSCode extension. The...
View ArticleOh no, we're toast because of PPX usage
We’ve found a solution and merged a PR for supporting Rescript 11! Now we’re working on record spread support.
View Article[feature-recuest] VSCode extension: show available variables within scope of...
Interesting idea. Is there something equivalent available in some other extension you know of?
View ArticleHow to setup a root bsconfig for rewatch?
Could you describe the desired logic of finding packages? I’ve added the pnpm support recently and am familiar with the part of the code. I can add support for this case if I understand the problem...
View ArticleOh no, we're toast because of PPX usage
The example from rescript-relay might be more helpful. I was quite lazy with rescript-schema since tests cover this part well.
View ArticleHow to setup a root bsconfig for rewatch?
Yeah, I list a few directories in the workspace.yaml file any any pnpm command I use always first checks these directories: packages: - app/client - packages/* I wouldn’t be opposed to adding...
View ArticleIssue with commiting res.js files without CI build step
Following the recommendations on this page Interop with JS Build Systems We also recommend that you initially check in those ReScript-generated JS files, as this workflow means: You can introduce...
View ArticleHow to setup a root bsconfig for rewatch?
The pinned-dependencies are actually useless right now and don’t have any effect. You can ignore them.
View ArticleHow to setup a root bsconfig for rewatch?
Could you create an issue in the rewatch repo and a minimal reproduction repository with your setup?
View Article[feature-recuest] VSCode extension: show available variables within scope of...
I haven’t seen any extension like that. I thought of it because i normally have many shallow but long functions or react components and I constantly need to be scrolling up and down and digging in to...
View ArticleClik here to view.
ReScript 11.1 uncurried issue with core package?
Hello, I’ve just upgraded my app from 11.0.0 to 11.1.0 and encounter an issue with the @rescript/core package which I’m not using I checked the @rescript/core package version in the node_modules and...
View ArticleClik here to view.
Are React components with many lines of code less performant?
I just watch this video Are Your React Components Too BIG? He shows how a big component rerenders the entire page on every click. I do use many big Rescript React components of thousands of lines of...
View ArticleReScript 11.1 uncurried issue with core package?
It’s probably because of rescript-classnames which has Core 1.0.0 as a dependency. And Core does not follow semver, it will be merged into the Compiler anyway. It’s a very small dependency though, I...
View ArticleAre React components with many lines of code less performant?
The only approach that has worked for me to avoid such large re-renders is to keep the state “outside” the component tree. Then, access that state only in the components that need it. Now only the...
View ArticleAre React components with many lines of code less performant?
Unless you have a huge list of items aka a table rerendered, this shouldn’t be an issue. So my suggestion is to keep calm, until your users actually start sending real complains.
View ArticleIssue with commiting res.js files without CI build step
That advice is a bit old now, although it might become viable again once core is pulled into the compiler rather than a dependency. Personally, I completely disagree with committing generated code -...
View ArticleOh no, we're toast because of PPX usage
Spice or updating Decco was probably the correct answer for you, but many years ago I grew tired of the performance overhead of running a PPX when the percentage of files it actually needed to process...
View ArticleAre React components with many lines of code less performant?
50-100 lines and I start breaking things up. I like tidy little files with a single purpose. It’s also easier to test little components. I find it easier to maintain performance this way as well.
View Article