fix(atomizer-plugins): run atomizer on file updates

[redonkulus]

I confirm that this contribution is made under a BSD license and that I have the authority necessary to make this contribution on behalf of its copyright owner.

---

Fixes the atomizer-unplugin library to run atomizer on application file updates. Code copied from @maheshbansod investigation.

[changeset-bot]

🦋 Changeset detected

Latest commit: 795b9a6

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
atomizer-plugins	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
acss-site	✅ Ready (Inspect)	Visit Preview	Dec 5, 2022 at 7:05PM (UTC)

[maheshbansod]

@redonkulus in my project, I'm planning to make this so that writeFile in transform will invoke during dev mode only - without the dev mode flag, transform will exit early and buildEnd will do the writeFile.
I think this will make build faster, since it doesn't have to update the file on every transform.

[redonkulus]

@maheshbansod how will you implement the dev mode flag, NODE_ENV=development?

Will you keep the transformIndexHtml hook as well as buildEnd? I think if you move it off of transform then the debounce may not be needed after all.

I misread your original comment, I think you were saying that you will only change to buildEnd when the dev flag is not passed in?

[redonkulus]

@maheshbansod I've added the dev flag check using NODE_ENV since vite already uses that standard. So now it will only call writeFile() in dev mode and leave writing to file in production for buildEnd.

[maheshbansod]

@redonkulus I was thinking of sending the dev flag via the options parameter but this way looks good.

[redonkulus]

Ok please test this out locally. I will merge and release tomorrow. Thanks!

[maheshbansod]

@redonkulus tested the code on my side in a Vite plugin. working well.