"esbuild-svelte" didn't set a resolve directory
See original GitHub issueWhen i use url() in css like:
content: url('img/img.jpg');
/* or */
background-image: url('img/img.jpg');
i have a error:
> fakecss:/path/to/Component.esbuild-svelte-fake-css:1:458: error: Could not resolve "img/img.jpg" (the plugin "esbuild-svelte" didn't set a resolve directory)
To Reproduce REPO
Expected behavior bundling url() to css 🤷🏻♂️
- esbuild-svelte version: latest
- esbuild version: latest
- Svelte preprocessors used (if any): sass
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Plugins - esbuild
An esbuild plugin is an object with a name and a setup function. ... If you want to resolve a path relative to...
Read more >SvelteKit could not resolve dependency even though it's external
I found discussion about this issues in SvelteKit repo ... I switched to bcryptjs and didn't get the error output, I couldn't get...
Read more >esbuild-svelte-inertia - npm Package Health Analysis - Snyk
Ensure you're using the healthiest npm packages. Snyk scans all the packages in your projects for vulnerabilities and provides automated fix ...
Read more >esbuild-svelte - npm
Plugin to compile svelte components for bundling with esbuild. Install. Install this plugin, esbuild and Svelte. A simple build script looks ...
Read more >TSConfig Reference - Docs on every TSConfig option
Lets you set a base directory to resolve non-absolute module names. You can define a root folder where you can do absolute file...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Fixed in
v0.5.5
Oh wow! That appears to be a bug in
rewrite-imports
. I’ll follow up later to confirm. Fix released inv0.5.6