Use a development component instead a build folder

[Toledodev]

I'm trying to implement the feature requested by Peerrich in calcom (calcom/cal.com#2939), but as the TimezoneSelect component is imported from the build, it makes it difficult to make some kind of change in the code.
In the example folder (example/src/Timezone.tsx), the TimezoneSelect is imported from dist folder

As it is, any changes made to the code will not reflect in the development, when we create a .tsx component for TimezoneSelect instead of importing from the build we will be able to see the changes at the same time as we do

[ndom91]

Ah yeah, I see what you mean. I always just used it to double check changes worked after build.

I'm testing in the main package.json changing the dev command from:

"dev": "cd example && npm run dev",

to

"dev": "concurrently \"rollup --watch\" \"cd example && npm run dev\"",

That way any changes in the source timezone/component files should be auto rebuilt and then visible in the example without any further major changes.

If yuo have any good ideas to remedy this though, I'm all ears 👍

[ndom91]

@Toledodev alright awesome, seems to work well. Just pushed to main, if you update your branch you should have an updated dev npm script that should do the trick 👍