New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: EISDIR: illegal operation on a directory, read when running rollup -c #186
Comments
Hard to say without more info. The manifest looks good. It seems that Rollup is trying to read a directory as a file. What version of RPCE are you using? |
The latest, tried both beta and stable |
@amiregelz I've done a major rewrite, would you mind giving it a try? The API has changed a little, you can see the updated instructions on DEV: Create a Vite-React Chrome Extension in 90 seconds - DEV Community 👩💻👨💻 |
i had the same problem as amiregelz and after following your vite-react tutorial it now works.
now it works like a charm! @jacksteamdev can i also just say that your blog post and comments are such a joy to read. i find them very comprehensible and user friendly. thank you for the effort you put into it all :) |
@flurrux Thanks for your kind words! Comments like yours make all the difference. 🤗 We probably need to add some validation, since manifest version 2 isn't supported. |
Added MV3 validation in #258 |
Added auto-copy for missing manifest assets in #259 |
It appears that this issue is now primarily a duplicate of #137, closing |
Build tool
Rollup
Where do you see the problem?
Describe the bug
Trying RPCE for the first time and using the simple starter snippet from the Usage section.
When I run
rollup -c
I am getting this cryptic error:I tried both on Windows and on Linux (mac).
This is my
rollup.config.js
:My
manifest.json
is standard as well:What should I investigate?
Reproduction
Just the basic usage example. my repo is private but is there anything I should investigate?
Logs
No response
System Info
Severity
blocking all usage of RPCE
The text was updated successfully, but these errors were encountered: