@rescript/runtime dependency problems
heh, no, esbuild fails as well: getting tons of these: ✘ [ERROR] Could not resolve "@rescript/runtime/lib/es6/Stdlib_Option.js" lib/es6/src/foundation/foundation_duration.res.js:3:31: 3 │ import * as...
View Article@rescript/runtime dependency problems
I recently had a similar thing with bun isolated installs. The runtime wasn’t found by vite and I had to work around that. Can you create a new discussion for this? That feels like worth talking more...
View Article@rescript/runtime dependency problems
Moved the posts here into a separate topic. It should work now: pnpm info rescript dependencies { '@rescript/runtime': '12.0.0' } pnpm info rescript optionalDependencies { '@rescript/linux-x64':...
View Article@rescript/runtime dependency problems
i don’t know what you mean when you say “it should work now”. your commands give the same output for me, but it still doesn’t build/bundle unless i have @rescript/runtime. is this a pnpm-related issue?
View Article@rescript/runtime dependency problems
Sorry, I should have written “if the missing npm tag was actually the issue, it should work now to install without explicitly adding @rescript/runtime”. What’s actually the issue is hard to say...
View Article@rescript/runtime dependency problems
maybe the issue is i have rescript under devDeps? which i thiink SHOULD be right but maybe isn’t? the tooling is conceptually for devDeps
View ArticleClik here to view.
@rescript/runtime dependency problems
That sounds like it. We suggest on the installation page to do a normal install: ReScript Documentation Installation | ReScript Language Manual ReScript installation and setup instructions Mainly...
View ArticleClik here to view.
Missing dependency in search path when using dynamic import
Has anyone encountered this before? As soon as I use Js.import() I get this error. Rescript v11. No idea where to begin debugging this. Thanks
View ArticleMissing dependency in search path when using dynamic import
Oh sorry, it’s Missing dependency X in search path where X is Js.import(X.make) (following the lazy component docs)
View ArticleTilia is born... still early version, ideas welcome :-)
Hello @gaspard, I created 2 issues in GitHub: For updating to ReScript v12 and also for migrating from Jotai Atoms. Currently I’ve migrated everything in the repository from Jotai Atoms (It’s still a...
View Article@rescript/runtime dependency problems
Since rescript includes the runtime, it should be a regular dependency.
View Article@rescript/runtime dependency problems
i don’t agree with this. since the runtime was actually separated, the right thing to do is keep rescript under devDeps and runtime under deps. there’s zero reason to install tooling in a deployed...
View Article@rescript/runtime dependency problems
The compiler got split per platform so it doesn’t add too much weight and if your project is very size sensitive, you probably use a tree shaker anyway! So I’d say the recommended setup is simple and...
View ArticleTilia is born... still early version, ideas welcome :-)
Hi Brian ! I replied on the github issues. Here is the link if others want to follow or join: github repo.
View ArticleIntroducing MoonBit and a few reflections from building the ReScript toolchain
@Hongbo one thing I wonder is how the /explain works in the IDE? It seems to do something LLM like about the current code, super cool. Is that talking to a local LLM? This even works in the web IDE...
View ArticleMissing dependency in search path when using dynamic import
Is this error in the actual build, or just in the editor?
View ArticleMissing dependency in search path when using dynamic import
It’s in the build, i.e. the terminal command rescript.
View ArticleMissing dependency in search path when using dynamic import
Could you create a minimal reproduction repo?
View ArticleMissing dependency in search path when using dynamic import
Yes, here you go: GitHub - benadamstyles/rescript-js-import-repro Reproduces reliably. Thanks!
View Article