You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using Parcel v2 for my web application, and I'm encountering an issue where the bundler fails to reload when I import modules using relative paths that point outside the root directory of my project. This issue is causing development delays, as I am unable to see changes made to the imported modules without manually restarting the bundler.
Steps to reproduce:
Set up a new project with Parcel v2
Create a file outside the root directory, e.g., ../external-dir/module.js
Import this file in the project using a relative path, e.g., import myModule from '../external-dir/module.js';
Start the development server with parcel serve index.html
Make changes to the module.js file and save
Expected behavior:
When I save changes made to module.js, I expect Parcel to automatically reload the development server and reflect the changes in the browser.
Actual behavior:
Parcel does not reload the development server after saving changes to module.js. I need to manually restart the bundler to see the changes in the browser.
The text was updated successfully, but these errors were encountered:
Description:
I am using Parcel v2 for my web application, and I'm encountering an issue where the bundler fails to reload when I import modules using relative paths that point outside the root directory of my project. This issue is causing development delays, as I am unable to see changes made to the imported modules without manually restarting the bundler.
Steps to reproduce:
Expected behavior:
When I save changes made to module.js, I expect Parcel to automatically reload the development server and reflect the changes in the browser.
Actual behavior:
Parcel does not reload the development server after saving changes to module.js. I need to manually restart the bundler to see the changes in the browser.
The text was updated successfully, but these errors were encountered: