ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
A diagnostic guide to Ceylon 1.3.3 module resolution failures: repository order, version range conflicts, stale caches, invalid .car archives, and Java interop native imports.
Import errors in Jule builds almost always trace to six causes: stale jule.mod, version conflicts, path casing, missing vendor dirs, private-module credentials, or compiler skew. Here's how to tell them apart and fix each.
When Ceylon reports a "cannot resolve module" error, the culprit is usually a missing or mismatched module descriptor, a bad module path, or version conflict. This guide walks you through the symptoms, a concise cause table, step‑by‑step checks, and targeted fixes—plus when to ask for help.
A diagnostic guide to Webpack 'Module not found' errors: read the resolver probe list, then fix extensions, aliases, file case or module roots.
I'm setting up a repeatable PureScript development environment with Spago (PureScript compiler 0.15.x, recent Spago) and keep hitting a module resolution failure I don't fully understand. After running spago install purescript-aff , importing Effect.Aff in a source file and running spago build fails with an error along the lines of Could not find module Effe
When running a k6 test that imports a local JavaScript module, the tool aborts with a “module not found” error before any virtual users start. The goal is to understand exactly how k6’s ES‑module resolver determines the file location for relative imports, especially when the test is launched from a directory different from the test file or when symlinks are
When webpack 5 targets a browser environment, imports of Node.js core modules such as fs trigger a resolution error if no explicit fallback is configured. This behavior stems from the removal of automatic polyfills for Node.js built-in modules starting in webpack 5, which previously provided implicit shims for node-targeted builds. The presence or absence of
Context A project uses moduleNameMapper to alias internal packages with absolute paths that resolve on developer machines. The same configuration fails in the production CI pipeline because the mapped paths do not exist in the container filesystem. Goal Define a single moduleNameMapper configuration that resolves correctly in both local development and the p
The goal is to have TypeScript path aliases work seamlessly in both local development (using ts-node or similar) and in the final production bundle created by Webpack. The constraint is that TypeScript’s paths option only influences the compiler’s module resolution and does not alter the import strings emitted into the JavaScript files, so the bundle still c
jule
webpack
purescript
k6
jest