Live reloading with custom JS about extension HOT 3 CLOSED

Great tip, that did it! @cezaraugusto I've tested and submitted a PR for here and updated docs, linked above.

from extension.

Hi there! Thanks!

If you are trying to load a source (not bundled) file in scripts/ and you get a $RefreshSig$ is not defined, that's a bug.

However if this file is bundled somewhere else outside Extension.js (like you said -- separately building and including in your extension), then scripts/ will fail if there are variables and imports outside the scope, as it has no access to the external bundling system. In this case, adding them to public/ might be the right choice. However, since it was designed for static assets, it does not listen for file changes.

I think having public/ to listen to file changes wouldn't affect existing functionality, but this is currently far from priorities. If you're feeling adventurous, editing the CopyPublicFolder file is the alternative for handling reload of public/ assets. I theorize that adding a listener to the change event in there would make your request possible. Something like:

watcher.on('change', (filePath: string) => {
  const target = path.join(output, path.relative(projectPath, filePath))
  this.copyFile(filePath, target)
})

The manual test would be adding a file to public/ and asserting that Extension.js reloads if they change. I added some instructions to run the project locally in CONTRIBUTING.md. If you want to give it a go, I can definitely review.

from extension.

Fixed by #64

from extension.