keystonejs/keystone

None of the codesandbox examples work

Open

#8462 opened on Apr 7, 2023

View on GitHub
 (9 comments) (1 reaction) (0 assignees)JavaScript (14,870 stars) (2,386 forks)batch import
help wanted

Description

This applies to all of the examples, when clicking the Codesandbox link it fails to build with an error. Error from this example is the following:

yarn run v1.22.19
$ keystone dev
✨ Starting Keystone
✘ [ERROR] Could not resolve "../example-utils"

    keystone.ts:2:30:
      2 │ import { fixPrismaPath } from '../example-utils';
        ╵                               ~~~~~~~~~~~~~~~~~~

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentationabout this command.

Codesandbox link: https://githubbox.com/keystonejs/keystone/tree/main/examples/usecase-blog

Contributor guide

Tech stack
typescriptnodejs
Domain
developer experiencetooling
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Node.jsTypeScript basicsMonorepo structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
The issue is that Codesandbox builds fail because the import '../example utils' in examples/like examples/usecase blog/keystone.ts resolves incorrectly in the isolated Codesandbox environment. To fix, examine the monorepo structure to understand the relative path from each example to the `example utils` module, which likely lives at the root or in a shared package. Then update the import paths in all affected examples (usecase blog and others) to use correct relative paths or a package reference. Test the fix by reproducing the Codesandbox build or running the examples locally. Also check if there is a workspace configuration (like `yarn workspaces`) that might need adjustment for Codesandbox.