Use browser
field in package.json
:
"browser": {
...
"package-name": false
}
Use browser
field in package.json
:
"browser": {
...
"package-name": false
}
First I tried the normal ways, like using html-to-react and the alike, but somehow due to some finicky formatting of strings, this library just flat out refuse to convert legitimate HTML. On top of that, NextJS was complaining loudly about Prop dangerouslySetInnerHTML did not match
.
Time to bring out the big guns.
Continue readingHow a simple config as such could be so hidden:
Handy snippet to run, to delete all but the current branch:
$ git branch | xargs git branch -D
$ git remote prune origin
Make sure that you have Microsoft’s Python extension installed. If you need more than one paths, simply create a .env
file in project root path, and add extra paths in, separated by :
, as such:
PYTHONPATH=libs/python:/another/python
VSCode will know to look for definitions under these paths.
If it still doesn’t work, or doesn’t work all the time, it’s very likely that one of the other plugins that you have is interfering with the Python one. To check, use Command + Shift + P to open the prompt and run the command:
> Extensions: Open Extensions Folder
Move all the extensions there to another temporary place, re-install the Python extension, and see if things start working now. If it does work now, add them back in batch to find out the culprit. 😀
Also, for gigantic projects, try switching intellisense engine:
Aka how to sending Arrays of Class Objects through GET
requests.
The catch with GET
is, of course, that you can’t under normal conditions send your request with a body of JSON objects.
Providing this was necessary during some painful email developments because:
This function is to be used as such:
// inside a component, grabbing `children` from the props:
<div>
{applyRecursiveProps(children, { style: {color: 'blue'} })}
</div>
Continue reading You can always start nodemon
right inside of VSCode, but I’ve found it a much better experience starting nodemon
in Terminal, and simply attaching VScode process to its --inspect
option.
It can be easily set up with a module resolver:
Continue readingIf 2-factor-authentication is enabled, an access token is needed in the place of password. Create one according to the steps here with the access for: