๐ Bug Report:
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, react, vite
- Domain
- build-system, frontend
Research direction
Start by running npm run dev and inspect the starter's imports of public/appwrite.svg and public/react.svg, using the Vite error output as the guide. Done means the development server starts without public-directory import errors and the referenced assets still load.
Written by the indexing model from the issue text.
Description
๐ Reproduction steps
npm run dev
๐ Expected behavior
[ASUS: starter-for-react]$ npm run dev
[email protected] dev
vite
VITE v6.3.5 ready in 471 ms
โ Local: http://localhost:5173/
โ Network: use --host to expose
โ press h + enter to show help
๐ Actual Behavior
Assets in public directory cannot be imported from JavaScript.
If you intend to import that asset, put the file in the src directory, and use /src/appwrite.svg instead of /public/appwrite.svg.
If you intend to use the URL of that asset, use /appwrite.svg?url.
Assets in public directory cannot be imported from JavaScript.
If you intend to import that asset, put the file in the src directory, and use /src/react.svg instead of /public/react.svg.
If you intend to use the URL of that asset, use /react.svg?url.
Files in the public directory are served at the root path.
Instead of /public/react.svg, use /react.svg.
๐ฒ Appwrite version
Appwrite Cloud
๐ป Operating system
Windows
๐งฑ Your Environment
17.0.0
๐ Have you spent some time to check if this issue has been raised before?
- I checked and didn't find similar issue
๐ข Have you read the Code of Conduct?
- I have read the Code of Conduct
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up โ it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from appwrite/starter-for-react
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
appwrite/starter-for-react#11 ยท
All issues in appwrite/starter-for-react
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
Mintplex-Labs/anything-llm#6490 ยท
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
[quality] workflow-scripts guard reads test:unit:coverage as skipping the unit suite, blocking #632 Openagent/quality hive/hosted-available-lke648397-260827-5n31 quality testing
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
area-clientside-dartpad
Difficulty 2/5 1-3 hours Newbie friendliness 62/100