I've copied over an .eslintrc file from my old React Native project to my new fresh React Native project and I'm getting errors in the WebStorm IDE saying it can't find any of the ESLint plugins and modules.
I've configured the project to use ESLint, .eslintrc and to use the local ESLint rather than global.
/usr/local/bin/node /Users/Projects/foo/node_modules/eslint/bin/eslint.js --format=checkstyle --stdin --stdin-filename screens/Root.js
Cannot find module 'eslint-config-airbnb'
Referenced from: /Users/Projects/foo/.eslintrc
Error: Cannot find module 'eslint-config-airbnb'
Referenced from: /Users/Projects/foo/.eslintrc
at ModuleResolver.resolve
I've checked and installed the modules using yarn add and I can' verify that they exist in node_modules, but it's still giving me the error messages.
Related
This post started out as a question, then I resolved the build issue I was experiencing in a hacky way. I wanted to share my findings for those that may have the same problem and see if anyone has a better resolution. Also, most of the posts I found related to this issue were created when Maui was still in beta. Lastly,
this issue affected the Android build only! The iOS build worked the first time.
Following this Microsoft Maui tutorial, I experienced a build issue right out the gate. The error was APT2260: resource mipmap/appicon and mipmap/appicon_round not found.
In the resources folder there was no appicon_round.svg file, so I copied appicon.svg to appicon_round.svg and tried a rebuild and got the same error.
I deleted android:roundIcon="#mipmap/appicon_round" from AndroidManifest.xml, and deleted the appicon_round.svg file I created via a copy action, but the build still failed.
Even though appicon.svg did exist, I removed android:icon="#mipmap/appicon" from AndroidManifest.xml, and the rebuild was successful. 🤦🏻♂️
Finally, I used Inkscape to create appicon_round.svg, I added it to the projects Resources/AppIcon folder, and then added android:icon="#mipmap/appicon" android:roundIcon="#mipmap/appicon_round" back to the AndroidManifest.xml file. The following build was successful.
First thing to note is that, while Visual Studio 2022 for MacOS did create the appicon.svg file, it did not generate the appicon_round.svg when I created the Multi-Platform project.
The second "gotcha" for me was when I removed the round SVG reference from the Android manifest file, but the build still failed.
A summary of how I resolved this issue is in my answer below. ⬇️
To summarize how to resolved the issue, if you generate a multi-platform project in Visual Studio 2022 for MacOS and any AppIcon SVG files are missing ...
Remove both/all AppIcon references from the AndroidManifest.xml
Build the app.
Generate the missing AppIcon SVG file(s) and put them in the correct folder.
Add both/all AppIcon references back to the AndroidManifest.xml
Build the app.
I have a Qt project with Visual Studio 2017. I tried to generate project files with premake and used the premake5.lua file from this page "https://wiki.qt.io/Premake_Project_Manager". this file uses a qt-support.lua module which is available on github. However, when I build my project with premake it shows the following error "qt-support.lua:707: action "qt" needs a description". Next, I download the example repository that is referenced in the official Qt documentation (https://github.com/annulen/qt-examples-premake) and tried to generate the project files for that. Even with their repository, it shows the same error. I haven’t used premake before and so I might probably be missing something obvious.
Try this one:
https://github.com/dcourtois/premake-qt
I've been using it for years and I'm very happy with it.
I'm using MSBuild to build a project with configuration set to a custom configuration. I have a referenced project (a library) which does not have any cutom configuration set to it. The issue is, it seems like MSBuild is building the project and the project references with the same configuration.
I'm using this command:
msbuild.exe <path>\<project>.csproj /p:DeployOnBuild=true /p:OutDir=<dirpath> /p:Configuration=<CustomConfig>
Im having the follow error:
C:\Program Files
(x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(724,5):
error : The OutputPath property is not set for project
'referencedProject.csproj'. Please check to make sure that you have specified a valid combination of Configuration and Platform for this
project. Configuration='CustomConfig' Platform='AnyCPU'. You may be seeing
this message because you are trying to build a project without a
solution file, and have specified a non-default Configuration or
Platform that doesn't exist for this project. [path\ReferencedProjectcsproj]
I cannot find anything related online, if anyone can point me to anything or help me out with this, that would be great.
I found a work around, posting it here in case someone ends up in the same scenario.
The project library did not have the custom configurtation so, i had to edit the csproj file to change the condition of build configuration to this:
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' Or '$(Configuration)|$(Platform)' != 'Debug|AnyCPU'">
This will force the compiler to take the leading configurations if it is in release mode or any custom configuration that is mentioned.
I have no found any way that will command MSBuild to choose different configuration project dependencies.
We recently switched from TFS2008 to TFS2010, and now one of our build definitions is failing on a strange error:
Building project "AAAA.cs".
It looks like it's trying to build a CS file. The file exists within a project, but the project builds locally without errors. I can't find it referenced anywhere (installer or solution file) as a project.
Groping at this point - does anyone have any thoughts?
Do you see this within the MSBuild log of the TFSBuild log? Is it possible you've included it in the list of solutions/projects to build in the Build Definition (if using the DefaultTemplate build workflow)?
Looks like we needed to install SP1 for VS2008 and the forward compatibility hotfix on the build server. It's still oddly building a CS file as a project, but the builds are now succeeding.
I am playing with a simple project based on Django framework. My IDE is PyDev/Eclipse.
I cannot make code completion work for Django code, but it works fine for standard Python libraries.
I tried to add Django dir (in my case C:\Program Files\Python26\Lib\site-packages\django) to PYTHONPATH both on PyDev level (Window->Preferences->PyDev->Interpreter - Python->libraries) and on a project level (Project->Properties->PyDev - PYTHONPATH) - no luck so far.
Can you please advise what I am missing here (preferably without installing PyDev extensions).
Ok I give it another try.
Eclipse in C:\test\eclipse
Python 2.6.2 in C:\test\python-2.6.2
Django 1.0.2 final in C:\test\python-2.6.2\Lib\site-packages -> only the actual django folder not the docs, example, and so on. I did this without running setup.py as descriped in the INSTALL file.
Added C:\test\python-2.6.2 and C:\test\python-2.6.2\Lib\site-packages to the PATH variable
As described here I set the Interpreter in Eclipse by Window > preferences > pydev > Interpreter > Python. This automatically included a whole bunch of things under System libs like (C:\test\python-2.6.2\;C:\test\python-2.6.2\DLLs;C:\test\python-2.6.2\lib\site-packages;....). A whole bunch of Forced Builtins are also found.
Then I made a new "Pydev Project" added a package and there a new module with a class and a module which imports the class and calls a function from it. During writing this pressed Crtl+Space several times, and builtins as well as the new stuff from my Module where shown by code completion.
I suggest Configuring pydev to work with django and
Getting started Eclipse/Pyddev
In the latter one there is a section specifically for code completion which mentions a problem with firewall or shell timeout. And in another section he mentions problems when (as in your case) the eclipse installations has spaces in the filepath
I solved setting the PYTHONPATH too.
In the pallet Projects, right-click on the project -> properties
In the PYTHONPATH configuration you have to put the folder that contains your project as a external folder.
Exemple:
/var/www/my_project
PYTHONPATH=/var/www/