Update README: synthwave84.css doesn't need to be copied to another location if it's already present in the extensions folder

[robb0wen]

Update README: synthwave84.css doesn't need to be copied to another location if it's already present in the extensions folder

[hadriengerard]

Update: I've done some tests and I realized that we have access to window.nodeRequire which gives us access to the FileSystem thanks to nodeRequire('fs').

So I updated the script and it now finds the right extension directory whatever the version number is.

No more need for tags names or internet access! It should load the synthwave84.css file from the extension directory after each update without having to change the path.

It also gets the user home directory with nodeRequire('os').homedir() and no more config is required except the declaration in settings.json like:

"vscode_custom_css.imports": [
    "file:///Users/username/.vscode/loadResourcesFromExtensionsDirectory.js" 
],

Let me know what you think of it 🙂

[robb0wen]

I originally wanted to do it this way. The issue I see though, is that the file-path to the extension changes every time it updates a version number. This means that any update to the extension will break the glow, regardless of whether or not the CSS file has changed.

Currently, copying it means that unless the glow CSS has been updated, it will persist as it was prior to the update.

There are definitely pros and cons to both methods.

I'd be interested to get more feedback as to which was preferred.

[robb0wen]

Nice! very cool work. I'll look to incorporate it in the next version.

[hadriengerard]

I also prefer @ranolfi's method because the css will remain up to date with the next updates of the extension.

Regarding the version number issue, I have made this little script which is load instead of the css file in vscode_custom_css.imports. It fetches the tag names from the repo and then look for a matching directory/file with the file:/// protocol, allowing to not worry about future updates.

This is probably not the best solution, plus it will not work without internet connection (I can probably add a fallback for this), but It should work with any extension.

[snd3r]

@hadriengerard works great!
I think the right place for this script is the Readme.md file.