See The Image！This appears after update to 2.2
But In Class A，the package is "com.example.roxas.myapplication.a"
UPDATE：AndroidStudio 2.2.1 is released！After the upgrade the problem has gone ！
The problem I met when I use Databinding.
If I remove the Databinding config in build.gradle,the problem fixed.
Why you have kept "com.example.roxas.myapplication.a" inside "com.example.roxas.myapplication"?
It should be "a" instead of "com.example.roxas.myapplication.a" in package "com.example.roxas.myapplication"
Related
I was just using typeorm with NestJS as usual. But it installed version 8.1.4 instead of my previously used 8.0.3. With the newer version I couldn't get the ormconfig.json working. I then checked and installed 8.0.3 and it worked again.
I have also tried with 9.0.0 and I couldn't get it to work their either.
Does somebody else has the same issue and maybe a temporary fix?
Thanks!
With #nestjs/typeorm#8.1.0 and on typeorm#^.3.0 is used, which doesn't use the ormconfig.json. You'd need to update your code to make the ormconfig work (i.e. get rid of it and follow the 0.3.0 format).
I installed angular cli via terminal. When I try to use ng(to create a new project), I get an error: Cannot find module './clone.js'terminal snap
I've tried to delete angular and clear cache, but that didn't help. Can somebody come up with solution, please?
graceful-fs, which is depended on by a LOT of npm packages, just released 4.1.12, which has a bug in it: https://github.com/isaacs/node-graceful-fs/issues/139
try upgrading to the new version of angular
ng update
In my nodeJS project suddenly it give error.I do not any upgrade or changes.
When I write NPM start in command line it give that error
ERROR in ./~/css-loader?sourceMap!./~/postcss-loader!./~/sass-loader?
sourceMap&outputStyle=expanded&includePaths[]=c:/TFS/rc1/app/scss&includePaths[]
=c:/TFS/rc1/~/compass-mixins/lib&sourceMap&sourceMapContents=true!./app/scss/_toolkit.scss
Module build failed:
undefined
^
Functions may not be defined within control directives or other mixins.
in c:\TFS\rc1\node_modules\compass-mixins\lib\compass\functions\_lists.scss (line 81, column 3)
# ./app/scss/_toolkit.scss 4:14-337
I reinstall compass-mixins package but it still give same error.Then I looked _lists.scss that file in 81 line there is a code .I deleted that bu it give same error.What should I do?
#if not(function-exists(compact)) {
#function compact($vars...) {
$list: ();
#each $var in $vars {
#if $var {
$list: append($list, $var, comma);
}
}
#return $list;
}
}
I also face the similar problem. And my project is using gulp-sass and compass-mixins. As heart.cooks.mind points out that, gulp-sass is depending on node-sass. And node-sass upgrade one of its dependence libsass to version libsass 3.3.3 Delorean since node-sass 3.5.1.
However, one of libsass 3.3.3 Delorean changes is related to this problem:
'Disallow functions to be defined in control directives or mixins (#mgreter, #1550)'
Obviously, _lists.scss in compass-mixins break this rule. Seems someone raise an issue to compass-mixins and they have idea on fixing it.
Before compass-mixins release the issue fixed version, my temporary workaround is to delete node_modules/node-sass manually and npm install node-sass#3.4.2
I had the same issue,please refer to node sass release 3.5.3 is breaking build and force lock gulp-sass to use the specific node sass library using shrinkwrap and avoid using the buggy version of node sass
I am using Gulp. Version 2.3.0 of gulp-sass breaks it. Go back to Version 2.2.0 and you are all fixed.
Edit:
The real culprit is the node module inside the "gulp-sass" node module known as "node-sass". You can see inside "gulp-sass"'s package.json file that it simply pulling version greater than ^3.5.3.
Even if you go back and reinstall "gulp-sass" to 2.2.0, as I suggested earlier, the package.json file in there will still pull "node-sass" greater than ^3.5.3.
If I use the older version of "node-sass" 3.4.2 that error goes away. I don't know how to fix that in an automated way. In a pinch I was able to fix the problem by copying that folder (that is using 3.4.2) from a different project that works. Now it compiles.
Can someone smarter than me figure out a better way to accomplish this result?
What I (temporarily) did, was to install globally the node-sass v3.4.2, and then replace the gulp-sass version of node-sass (it is located within gulp-sass/node_modules) with this older one.
sudo npm install -g node-sass#3.4.2;
sudo cp -r /usr/lib/node_modules/node-sass/ /usr/lib/node_modules/gulp-sass/node_modules/;
Btw, there is a PR waiting to be merged for this. But if you want to use this today then there's a fork of the merge too.
If you want to use latter then just put compass-mixins: tjenkinson/compass-mixins in your package.json and all will be good.
Update:- There's also an npm package for the latter mentioned in the PR now
Update 2:- This should no longer be a problem with v0.12.8 now
Orchard 1.8. While I can package the default theme successfully (TheThemeMachine) Using the command line instructions from here E.g
orchard> package create TheThemeMachine C:\Temp
packaging my own themes I get the following error
"Cannot create a package that has no dependencies nor content."
(the theme indeed has content)
Anybody have the same issue ? Rookie error I'm guessing..But help much appreciated as error appears undocumented.
This error happens when you have set wrong version for the module/theme. For NuGet it's important to have correct versioning. Make sure you have version in your Theme.txt following formats {x.x}, {x.x.x}, {x.x.x.x} (where x are only digits, each up to 10)
Valid:
1.0
0.0.0.1
01.4423.455.112312
1234567890.1234567890.1234567890.1234567890
Invalid:
1
.1
1.1.1.1.1
1.12345678901
When you switch to the nvm to manage your node versions, should you point your node interpreter to that one?
ie from /usr/bin/node to the ~/.nvm/v.xxx one
I ask because I'm running into some issues with webstorm when trying to debug node stuff now.
Best thing I've found so far is to add each version to Default 'Node.js and NPM' Settings (rather than in individual Project settings). Then when creating new projects, or updating existing ones, you can select that version from the dropdown instead of having to recreate it for each project.
But it would be nice if the NodeJS Plugin would look for nvm and integrate with it. Or if nvm would create symlink for /usr/bin/node and update that when you change the version.
Yes, you need to explicitly set the Node Interpreter to the version you'd like to use
You should not need to do that, it seems it was a bug that was identified and reported. A fix will be released in the coming 2016.1.3 EAP version of WebStorm.
https://youtrack.jetbrains.com/issue/WEB-21558
As #zenw0lf stated above, WS does now look for installed node versions under .nvm but since .nvm does not yet add an alias for the active version of node, the specified value is fragile as it's version-based.
I've attempted to resurrect the appropriate issue in NVM to alleviate this. Please follow that for updates.