In a Node.js app with installed npm dependencies, I'm importing a module like that:
import { Admin } from 'react-admin';
When I hover on the 'Admin' name and choose 'Go to definition', VSCode displays the compiled source, taken from node_modules/react_admin/lib/index.js, instead of the more readable, ES6 source located under node_modules/react_admin/src/index.js.
How can I (or the 'react-admin' package author) tell VSCode to jump to the non-compiled source when hitting 'go to definition'?
Related
I'm new to web development and found a website prototype, but when I tried to open it by clicking on the index.html in the files, it's completely blank. The only thing I see is on the tab, and it just says "React App".
How do I make the website components actually show? I know there should be something showing because I can see all of the code and pages, but nothing shows?? Is there some other way to open the website?
React is a library that compiles all your javascript then renders it in index.html file. If you open the file directly you won't see anything. If you want to run your project then:
Open the project folder in vscode.
Press CTRL+J if you have windows.
Type npm install - It will install all project dependencies listed
in package.json at the root of your project.
Then run npm start - This will start development server locally
that you can use to develop your project as you go.
Then go to App.js and make changes and see how the server
automatically refreshes.
to learn more, go to Get started with react - FreeCodeCamp
When building Mono DLLs for use in Unity we want to reference the UnityEngine.dll. Several tutorials talk through how to do this. For example here are the instructions from the Unity manual
Next, you should add references to the Unity DLLs. In MonoDevelop, you
should open the contextual menu For References in the Solution Browser and
choose Edit References. Then, choose the option .Net Assembly tab > File
System > select file. [...]
At this stage, you will have the option to select the required DLL file. >On Mac OSX, the file can be found at
Applications/Unity.app/Contents/Frameworks/Managed/UnityEngine.dll
But the Mac finder will not step into Unity.app so I cannot navigate into that folder to choose UnityEngine.dll. I can navigate there in the terminal, but not in the 'select file' finder. How do I add UnityEngine.dll as a reference in a Mono project on a Mac?
Seems like MonoDevelop does not set the file browser to include .app and thus does not present Show Package Contents in the right-click context menu.
Use CMD-Shift-G to popup the Go to the folder: entry, enter /Applications/Unity.app/Contents/Frameworks/Managed and select Go
In WebStorm, I am getting a "Project SDK is not defined" prompt when editing the app.config file of my elastic beanstalk environment, and the file is full of red squiggly line errors, as follows:
When I click the "Setup SDK" link, I am taken to the following screen:
What should I do to get WebStorm to recognize my app.config file?
The file type of Elastic Beanstalk config files are YAML, but from your screenshots, it looks like your WebStorm thinks that they are something else. To get WebStorm to treat config files as YAML, do the following:
Make sure the YAML Plugin is installed
Hit Ctrl+Alt+S
Type Plugins
Click on Plugins on the left side
Type YAML on the right side to install it or verify it's there already
Get WebStorm to treat *.config files as YAML
Hit Ctrl+Alt+S
Type File Types
Click on File Types on the left side
Click on YAML under Recognized File Types
Click the green + button under Registered Patterns to add *.config
WebStorm should then recognize your app.config file as a YAML file and no longer prompt you to set up an SDK while viewing it.
I am hoping to get autocompletion within PhpStorm while I am configuring Gruntfile.js files.
I believe I am not gettting code assistance for grunt methods like grunt.loadNpmTasks, grunt.initConfig etc because grunt is installed globally in my home dir /home/user/npm/lib/node_modules and not available locally in My project directory.
How can I enable code assistance (autocompletion etc) in phpstorm?
In the newest version of PhpStorm (2016.3), follow these steps:
Navigate to Preferences > Languages & Frameworks > JavaScript > Libraries
Press the "Download..." button.
Make sure "TypeScript community stubs" is selected from the dropdown at the top.
Find and select "gruntjs" and click the "Download and Install" button. The IDE will download the type definition file and the window will close when it's done.
Make sure the checkbox next to "gruntjs-DefinitelyTyped" is checked, then press "OK".
Next, open up your Gruntfile.js and add the following docblock at the top, right before the module.exports line:
/**
* #param {IGrunt} grunt
*/
module.exports = function (grunt) {
In Sublime Text 2, what steps do I need to take to get Syntax Highlighting for the Laravel Blade Template Engine to work?
As described in http://daylerees.com/2012/04/06/notable-blade-syntax-support-by-medalink/, I took https://github.com/Medalink/Laravel-Blade, unzipped it and copied the folder into Sublime's packages folder.
However, it doesn't seem to work (see screenshot), even if I set it manually using Tools\Command Palette...\Set Syntax: Blade
Is this only meant to work with particular Color Schemes (if so, which ones), or what am I missing? (I just started using Sublime Text today)
The easiest way to install plugins for Sublime Text 2 is through Package Control.
To install Package Control:
Installation is through the Sublime Text 2 console. This is accessed via the ctrl+` shortcut. Once open, paste the following command into the console:
import urllib2,os; pf='Package Control.sublime-package'; ipp=sublime.installed_packages_path(); os.makedirs(ipp) if not os.path.exists(ipp) else None; urllib2.install_opener(urllib2.build_opener(urllib2.ProxyHandler())); open(os.path.join(ipp,pf),'wb').write(urllib2.urlopen('http://sublime.wbond.net/'+pf.replace(' ','%20')).read()); print 'Please restart Sublime Text to finish installation'
This command creates the Installed Packages folder for you (if necessary), and then downloads the Package Control.sublime-package into it.
When you have Package Control installed all you need to do to install the Blade syntax highlighter is to:
Open the command palette and type "install package"
Press enter
Wait for a new palette to show up after it has fetched the package list
Type "blade syntax"
Press enter
Enjoy
For Sublime text 3 as well as sublime text 2
install Sublime Package Control (more help on: http://wbond.net/sublime_packages/package_control/installation)
then restart sublime text (2/3)
and press ----> control (or command in mac) + shift + p
there search for package control: install package
wait for another interaction screen
search for Laravel Blade (and other packages if you want)
{
For video tutorials on this and other , subscrive this channel : https://www.youtube.com/channel/UChEv_j3fE4k2r7KcEApFDyQ
}
Also, once you have Package Control installed, you should also install the package 'DetectSyntax'. It will automatically detect the blade syntax so you don't have to manually set it for each file.
In case you installed the Laravel Blade Syntax Highlighter using Package control, that plugin, for some reason keeps throwing out errors.
Package Control: The package specified, laravel-blade, is not available
What I did is just Preference > Browse packages and then rename the folder into laravel-blade. Seems working with no pesky errors now. What I did is just gut feel. I did not even read anything in the files in the folder.
--
Edited: Go to Preference > Browse packages > Package Control.sublime-settings and remove the offending entry.
mine was stored in users folder, just do a folder search for "laravel-blade" and remove the entry from json config
Find: laravel-blade
Where: /Users/:username/Library/Application Support/Sublime Text 2/Packages