Remove outdated js snippet caveat on imports

[crajcan]

I'm not sure if import statements are universally implemented now but myself and others seem to be having success using them in snippets.

[daxpedda]

I honestly don't know anything about this limitation.
Going through git blame didn't help either.

@Liamolucko do you know something about the historical context here? Testing it out locally seems to work fine for me.

[Liamolucko]

@Liamolucko do you know something about the historical context here? Testing it out locally seems to work fine for me.

No, but I found the original RFC for snippets and there's a note about it there. It looks like what the caveat's supposed to mean is that imports don't work relative to the original path of the snippet like you'd expect, but there's nothing stopping you from writing them anyway and having them be resolved relative to the final path of the snippet. The fact that that works seems to be an unintended side effect of not processing the JS at all.

[daxpedda]

Thank you!
@crajcan at best I would update the documentation then instead of removing it.