search

loftyshaky / advanced-extension-reloader

MIT License
8 stars 0 forks source link

Build process failing due to missing 'shared_clean' module #4

Closed kavwad closed 1 month ago

kavwad commented 2 months ago

I'm hitting some errors while trying to build this project. Here's what's going on:

  1. Initial error: When running npm run prod, I received an error related to dist/dependencies.json:

    Error: /Users/.../advanced-extension-reloader/dist/dependencies.json: ENOENT: no such file or directory, open '/.../advanced-extension-reloader/dist/dependencies.json'

  2. Attempted fix: I created the file and initialized it with an empty array:

    echo '[]' > dist/dependencies.json

  3. Subsequent error: Now, the build process progresses further but fails with multiple errors related to a missing 'shared_clean' module. For example:

    ERROR in ./src/ts/background/background.ts 4:0-31
Module not found: Error: Can't resolve 'shared_clean/internal' in '/.../advanced-extension-reloader/src/ts/background'

  4. Current state:

    • The @loftyshaky/shared package is installed in node_modules.
    • There's no 'shared_clean' directory under '@loftyshaky' in node_modules.
    • The project does have a src/ts/shared_clean directory with relevant imports.

Do you have any suggestions for how to set up or build the 'shared_clean' module? Thanks so much.

loftyshaky commented 2 months ago

I'm in the process of updating the extension. Pushed these changes too soon, should've created a different branch...

Please return to the old commit, do something like: git clone https://github.com/loftyshaky/advanced-extension-reloader git reset --hard c93150aa738eeb13a755f42d3fa6f0e9c7c3c94d

And you'll be on the last version that is published in CWS. It should build.

kavwad commented 2 months ago

This worked! Thanks so much. Let me know when I should fast forward. Thanks for making this!

loftyshaky commented 2 months ago

I'll make sure to notify you. I'm hoping to finish the update in a few days.

loftyshaky commented 1 month ago

The issue has been resolved. Could you please confirm if the fix works as expected?

kavwad commented 1 month ago

Updated and it works great! I've only tried manual reloading so far but I didn't run into the npm run prod error from before. Thanks!