You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which references the types file by an absolute path that includes a user name. I will have to copy this to a local directory if I want to put it on git or share it with others. As there is already a libraries directory in a new project, could the types file be created there as well, and referenced with a relative path in the config file?
This could be a toggleable option, but I don't see too much problem in just having the file copied in by default.
Thanks
The text was updated successfully, but these errors were encountered:
Good idea! When I made this I was trying to minimize how many files the project required, and at the time it seemed to make more sense to simply add the json file rather than the type definitions... Will definitely consider adding this in, and of course feel free to make a pull request if you are so inclined.
Currently creating a new project results in this generated
jsconfig.json
fileWhich references the types file by an absolute path that includes a user name. I will have to copy this to a local directory if I want to put it on git or share it with others. As there is already a
libraries
directory in a new project, could the types file be created there as well, and referenced with a relative path in the config file?This could be a toggleable option, but I don't see too much problem in just having the file copied in by default.
Thanks
The text was updated successfully, but these errors were encountered: