-
I've followed the guide here: #59, everything is working fine and see the demo site on my browser. when i run 'npm run build' (--force as well), even though i see the change made in index.js the final event-calendar.min.js does not include the change. When i am running npm run dev, i can see the changes in the console, but still the final js does not include them: Any ideas? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
Can you please check your $ ls -l node_modules/@event-calendar/
build -> ../../packages/build/
core -> ../../packages/core/
day-grid -> ../../packages/day-grid/
interaction -> ../../packages/interaction/
list -> ../../packages/list/
resource-time-grid -> ../../packages/resource-time-grid/
resource-timeline -> ../../packages/resource-timeline/
time-grid -> ../../packages/time-grid/ If this is not the case, then try the following:
cd packages/build
npm link
cd ../core
npm link
...
(and so on)
rm -rf node_modules/@event-calendar/*
npm link @event-calendar/build @event-calendar/core ... (and so on) |
Beta Was this translation helpful? Give feedback.
-
Hmm, I thought it was a linking problem. I am using Windows 10 here, so my guess is this is a windows issue. The 'npm link @event-calendar/build' part, didnt work as expected. Each line was just creating a link for that specific folder, but it was undoing the previous symlink changes from the previous commands. So basically in the end I was left with just the 'time-grid' folder link. |
Beta Was this translation helpful? Give feedback.
-
Uh, good to know, thanks |
Beta Was this translation helpful? Give feedback.
Can you please check your
node-modules/@event-calendar
directory? There should be symlinks like this:If this is not the case, then try the following:
packages
directory and runnpm link
:node_modules/@event-calendar
directory: