My CSS doesn't work. Here is my terminal log:
$ gulp sass
Using gulpfile ~/dev/myproject/gulpfile.js
Starting 'sass-ionic'...
Starting 'sass-myproject'...
Individual stylesheets must be in the sass directory.
{ [Error: Compass failed]
message: 'Compass failed',
fileName: '/Users/me/dev/myproject/scss/main.scss',
showStack: false,
showProperties: true,
plugin: 'gulp-compass',
__safety: { toString: [Function] } }
Finished 'sass-ionic' after 634 ms
I am using Ionic Framework.
The funny part is that I have two computers with pretty much same setup and the other works fine and the other gives the error above. I'm using git so the both projects have identical files and folder structure.
EDIT: After downgrading compass:
Here is what I get after 'gulp sass':
Starting 'sass-ionic'...
Starting 'sass-murikka'...
Finished 'sass-ionic' after 614 ms
warning Webkit only supports pixels for the start and end stops for radial gradients. Got: 100%
warning Webkit only supports pixels for the start and end stops for radial gradients. Got: 100%
identical ./www/css/main.css
Finished 'sass-murikka' after 843 ms
Starting 'sass'...
Finished 'sass' after 13 μs
On the other computer I get exactly the same output except
identical ./www/css/main.css
-->
overwrite ./www/css/main.css
For anybody stumbling across this bug on a Windows environment, first check your config paths to ensure they're not absolute or some other nonsense.
Next, make sure you use the correct case with your directories when navigating to your project directory. Since Windows is case-insensitive, it will allow you to cd myproject/source/ when it's actually MyProject/source/. gulp-compass will give this error if you run your gulp task using just cd myproject/source/ lower case.
Check your terminal CWD and make sure it matches the case: $ MyProject/source/ > gulp sass or some such.
Check if Ruby is installed in your computer. I had the same error and installing ruby solved the problem
Related
I have a Windows 10 laptop where no TeX distribution was ever installed before (double-checked for config directories, files, and environment variables).
Wanting to install TeX Live 2021, I followed the full installation guide and also read the Windows-specific warnings. I've now tried several times, following different installation procedures - cleaning up everything (deleting base & user directories, environment variables, etc) before each time - but still don't manage to get a working installation. Before I report a bug at tex-live#tug, I wanted to ask for advice here, in case I'm doing something wrong. Here is what I did, step by step, and the problems I encountered in the process.
1. First I tried running the recommended online installer install-tl-windows.exe. It never got past the screen that tries to contact or load from a repository, even after a 30-min wait. Tried a dozen times, choosing different mirrors nearby and far away. No luck.
2. Then I downloaded and unpacked the install-tl.zip and run install-tl-windows.bat therein. This time the main installation window appeared. I left all default paths and environment variables (note that I do have write access to C:); in the selection scheme I unselected all languages except US & UK English, unselected XeTeX, LuaTeX, ConTeXt; also unselected TeXworks (I use Emacs), and clicked Install. After one to three hours (depending on the mirror I chose), the installation was complete.
I tried compiling a minimal latex document (see below), and got an error similar to the one in this old question:
I can't find the format file `pdflatex.fmt'
Following the advice in the answers to that question and similar questions elsewhere online such as this, I tried running texhash and fmtutil-sys --all. The latter gave the error
no appropriate script or programme found fmtutil.
for which there are also many posts online.
2a. Not understanding what the problem could be, I re-tried with all possible combinations of the following three options: (a) choosing different mirrors; (b) leaving the full selection of packages (ie without unselecting some languages, LuaTeX etc); (c) redoing the procedure by choosing "Run as Administrator". No luck.
3. At this point I tried downloading the ISO file with the full installation. Mounted the image and run install-tl-windows.bat (as normal user, as recommended; I repeat that I do have write access to C:). Everything proceeded as in step 2. above. At the end of the installation I tried running pdflatex on the minimal latex document. New error this time:
This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2021/W32TeX) (preloaded format=pdflatex)
restricted \write18 enabled.
entering extended mode
(./minimal-template.tex
LaTeX2e <2020-10-01> patch level 4
L3 programming layer <2021-02-18>
! LaTeX Error: File `article.cls' not found.
Very strange. A file search revealed that article.cls is in the TeXLive file system; but kpathsea did not see it indeed.
4. At this point I opened the TeX Live Shell from the Start Menu; selected a CTAN mirror; updated the TL Manager which was not up to date; updated all packages; run Regenerate filename database; and run Regenerate formats. With the latter I got this error:
tex live shell:
mtutil [INFO]: total formats: 59
fmtutil [INFO]: exiting with status 53
C:\texlive\2021\bin\win32\runscript.tlu:915: command failed with exit code 53:
perl.exe c:\texlive\2021\texmf-dist\scripts\texlive\fmtutil.pl --sys --all
Here is a snip from the full set of errors appearing in the "Other" tab (I'm replacing my user directory with asterisks for privacy; note that I do have write access to these directories):
start load https://www.nic.funet.fi/pub/TeX/CTAN/systems/texlive/tlnet
finish load https://www.nic.funet.fi/pub/TeX/CTAN/systems/texlive/tlnet
start load http://contrib.texlive.info/current
finish load http://contrib.texlive.info/current
running mktexlsr ...
done running mktexlsr.
running mtxrun --generate ...
done running mtxrun --generate.
running updmap-sys ...
done running updmap-sys.
regenerating fmtutil.cnf in C:/texlive/2021/texmf-dist
running fmtutil-sys --byengine luatex --no-error-if-no-format --no-error-if-no-engine=luajithbtex,luajittex,mfluajit --status-file=C:\Users\***\AppData\Local\Temp\rPSb0Dpak2\WW_dJvUHgX ...
tlmgr.pl: fmtutil-sys --byengine luatex --no-error-if-no-format --no-error-if-no-engine=luajithbtex,luajittex,mfluajit --status-file=C:\Users\***\AppData\Local\Temp\rPSb0Dpak2\WW_dJvUHgX failed (status 255), output:
Unknown option: status-file
Try "fmtutil --help" for more information.
C:\texlive\2021\bin\win32\runscript.tlu:915: command failed with exit code 255:
perl.exe c:\texlive\2021\texmf-dist\scripts\texlive\fmtutil.pl --sys --byengine luatex --no-error-if-no-format --no-error-if-no-engine=luajithbtex,luajittex,mfluajit --status-file=C:\Users\***\AppData\Local\Temp\rPSb0Dpak2\WW_dJvUHgX
running fmtutil-sys --byengine luajithbtex --no-error-if-no-format --no-error-if-no-engine=luajithbtex,luajittex,mfluajit --status-file=C:\Users\***\AppData\Local\Temp\rPSb0Dpak2\WW_dJvUHgX ...
I tried to continue anyway with Regenerate fontmaps, and then tried again pdflatex on the minimal document. New error:
This is pdfTeX, Version 3.141592653-2.6-1.40.23 (TeX Live 2021/W32TeX) (preloaded format=pdflatex)
restricted \write18 enabled.
---! c:/texlive/2021/texmf-var/web2c/pdftex/pdflatex.fmt made by different executable version
(Fatal format file error; I'm stymied)
5. I tried again steps 3. and 4., but with "Run as Administrator". Same errors.
OK at this point I give up and really don't know what to do. Am I doing something wrong? For the moment I have to concur with this post: installation of TeX Live 2021 is an utter failure.
Here is the minimal latex file I used for testing (copy & paste):
\documentclass{article}
\begin{document}
test
\section{Section}
test
\end{document}
Found, that the download is not working because the system path to "cmd.exe" is not found. Therefore: open a cmd window and add the system path prior to starting the .bat file (set PATH=%PATH%;C:\Windows\system32)
I am using stencil with #bigcommerce on the following software:
Windows 8
Node.js 7.10.0
Python 2.7.14
NPM 5.6.0
After running stencil start and then loading the site at the local URL it gives me an error like this:
[Browsersync] File event [change] : stencil/*.css
{ Error: layout\pdp.scss doesn't exist!
at options.error (C:\Users\Tyler\AppData\Roaming\npm\node_modules\#bigcommerce\stencil-cli\node_modules\#bigcommerce\node-sass\lib\index.js:277:32)
formatted: 'Error: layout\\pdp.scss doesn\'t exist!\n on line 207 of my-theme.scss\n>> #import \'layout/pdp\';\n --------^\n',
message: 'layout\\pdp.scss doesn\'t exist!',
column: 9,
line: 207,
file: 'my-theme.scss',
status: 1 }
The line in the SCSS file causing this is:
#import 'layout/pdp';
Now, on my co-worker's Mac this works. SASS looks for ./layout/_pdp.scss and it loads just fine. But on my Windows PC this doesn't work. I've tried every variation of the import by including the underscore, including the extension, using ./ at the beginning, etc. Nothing seems to work.
Does anyone know why this wouldn't work on Windows or with these versions of NPM, NodeJS, etc.?
{ Error: EPERM: operation not permitted, open 'C:\Users\Vivek Sharma\apps\testAp
p\www\assets\imgs\Thumbs.db’
**errno: -4048,
code: ‘EPERM’,
syscall: ‘open’,**
path: ‘C:\Users\Vivek Sharma\apps\testApp\www\assets\imgs\Thumbs.db’ }
[03:09:32] deeplinks started …
[03:09:32] deeplinks finished in 110 ms
[03:09:32] ngc started …
[03:09:59] ngc finished in 26.71 s
[03:09:59] preprocess started …
[03:09:59] preprocess finished in 3 ms
[03:09:59] webpack started …
[03:11:33] webpack finished in 94.64 s
[03:11:33] uglify started …
[03:11:33] sass started …
Error: EPERM: operation not permitted, open ‘C:\Users\Vivek Sharma\apps\testApp
www\assets\imgs\Thumbs.db’
(node:14288) PromiseRejectionHandledWarning: Promise rejection was handled async
hronously (rejection id: 1)
[03:11:36] sass finished in 2.99 s
[03:11:36] cleancss started …
[03:11:40] cleancss finished in 3.62 s
[03:12:08] uglify finished in 34.76 s
---------------------END-----------------------------------
This error occurs when trying to build apk. using ionic cordova build android --release --prod in windows cmd
ionic v-3.19.0
cordova -v-8.0.0
node -v-8.8.3
npm -v-5.3.0
WINDOWS 8.1 64 bit.
full control is given to the system.
enter image description here
please help
Thank you, Developers, for responding to my query. I have resolved the issue. The problem was, Windows keeps building Thumbnails and stores them as Thumbs.db on the system.This prevents the system from copying, moving, deleting or renaming a folder. I prevented further caching of thumbnails and deleted the Thumbs.db from the project folder.
This is the procedure if anyone else comes across this problem:
1. Disabling Thumbs.db:
https://www.nextofwindows.com/what-is-thumbs-db-files-and-how-to-disable-and-remove-them
2. Next, to remove Thumbs.db:
https://www.youtube.com/watch?v=N7MgnYCMvHE
This will do the job. :)
Seems like your folder name has a white space try to rename the folder name and try to run it again.
Existing Path:
C:\Users\Vivek Sharma\apps\testAp p\www\assets\imgs\Thumbs.db
Change Path like this:
C:\Users\VivekSharma\apps\testApp\www\assets\imgs\Thumbs.db
You could see whitespace in between Vivek Sharma change it to VivekSharma For more info check this out:
Error: EPERM: operation not permitted
When I tried to generate with yo jhipster on Windows 7 32 bits machine, I got the below error:
bower json3#~3.2.5 progress received 3.7MB of 4.9MB
downloaded, 75% libjpeg-62.dll: downloading [===================]
100% 0.0s
? pre-build test failed, compiling from source...
d:\Self_jhipster\node_modules\grunt-contrib-imagemin\node_modules\jpegtran-bin\
lib\check.js:19
throw new Error('building is not supported on ' + process.platform);
^ Error: building is not supported on win32
at d:\Self_jhipster\node_modules\grunt-contrib-imagemin\node_modules\jpegtran-bin\lib\check.js:19:10
How to solve this error?
I'm the author of http://jhipster.github.io/ which is the generator your are referring to.
I have found your problem, it is indeed a bug in jpegtran-bin. I have updated all the dependencies in Grunt.js, and it should now work fine on Windows.
This will be commited in the next release (0.2.1), which should be out in a few hours.
You can also submit a bug at https://github.com/jhipster/generator-jhipster/issues
After google with more correct keywords, the solution from https://github.com/gruntjs/grunt-contrib-imagemin/issues/109 works for me.
In application's package.json, add "jpegtran-bin": "0.2.0" before
the reference for imagemin,
Remove node_module folder locally.
Run npm install again.
So i create a default meteor app.
Its runs great.
Now I add a simple insert in the startup function.
its is now giving me exceptions.
Here is my app.js code:
Book = new Meteor.Collection("book");
if (Meteor.isClient) {
Template.hello.greeting = function () {
return "Welcome to app_01.";
};
Template.hello.events({
'click input' : function () {
// template data, if any, is available in 'this'
if (typeof console !== 'undefined')
console.log("You pressed the button");
}
});
}
if (Meteor.isServer) {
Meteor.startup(function () {
if (Book.find().count() === 0) {
var names = ["Ada Lovelace",
"Grace Hopper",
"Marie Curie",
"Carl Friedrich Gauss",
"Nikola Tesla",
"Claude Shannon"];
for (var i = 0; i < names.length; i++)
Book.insert({name: names[i], score: Math.floor(Math.random()*10)*5});
}
});
}
And here is the exception I am getting:
No dependency info in bundle. Filesystem monitoring disabled.
Errors prevented startup:
Exception while bundling application:
Error: ENOTEMPTY, directory not empty 'C:\Users\Office\Workspace\Code\Meteor\app_01\.meteor\local\build\server'
at Object.fs.rmdirSync (fs.js:456:18)
at Object.module.exports.rm_recursive (C:\Program Files (x86)\Meteor\app\lib\files.js:256:10)
at C:\Program Files (x86)\Meteor\app\lib\files.js:254:15
at Array.forEach (native)
at Function._.each._.forEach (C:\Program Files (x86)\Meteor\lib\node_modules\underscore\underscore.js:79:11)
at Object.module.exports.rm_recursive (C:\Program Files (x86)\Meteor\app\lib\files.js:252:9)
at _.extend.write_to_directory (C:\Program Files (x86)\Meteor\app\lib\bundler.js:493:11)
at Object.exports.bundle (C:\Program Files (x86)\Meteor\app\lib\bundler.js:685:12)
at exports.run.restart_server (C:\Program Files (x86)\Meteor\app\meteor\run.js:615:26)
at C:\Program Files (x86)\Meteor\app\meteor\run.js:726:9
Please fix the problem and restart.
The console gives me no useful information at all.
Some more info:
I am using the windows version of meteor 0.5.4
My code has both tabs and spaces as indentation (should that be a problem?)
to add to my perplexity:
If i run the leaderboard example, it runs perfectly.
When I run the default project with my modified startup code, i get the exception. >.<
More info:
when the server crashed, the mongod service was still running in windows. In my infinite wisdom, i thought I'll kill it and maybe try a fresh restart of it.
now i get a new error:
PS C:\Users\Office\Workspace\Code\Meteor\app_01> meteor
[[[[[ C:\Users\Office\Workspace\Code\Meteor\app_01 ]]]]]
Unexpected mongo exit code 100. Restarting.
Unexpected mongo exit code 100. Restarting.
Unexpected mongo exit code 100. Restarting.
Can't start mongod
MongoDB had an unspecified uncaught exception.
Check to make sure that MongoDB is able to write to its database directory.
Edit: now deleted the .meteor/local/db contents. we are now back to the ENOTEMPTY error.
It is because the directory is not getting deleted during the bundling operation.
So when this happens, Stop your server with ctrl + c.
Then delete the contents of .meteor\local\db directory as well as .meteor\local\builds directory and run the server again using meteor command.
Not an ideal way, but it works.
Just tested this on my mac and on my Windows machine, it works fine for me. (Copied and pasted your code into app.js, did not change anything anywhere else, as I understood this is what you did).
There are two ways to go on:
You try meteor reset. Warning: This will empty any databases you had within this app, but I think there isn't anything all to important in there at the moment?
You delete the app and make a new one using meteor create appname, and copy the source code from above into app.js.
I think investing too much time and effort is not worth it, since it is not an app close to production stage. If, however, creating a new app causes the same problem, it will get interesting =)
EDIT: Just searched around and found this: https://github.com/TomWij/meteor/issues/18
Scroll down to the answer; apparently it might be your antivirus scanner preventing Meteor from rebuilding it. Is that possible?
Also, are you starting Meteor from anything else than cmd.exe? I just read through the issue on GitHub, and things seem to be pretty gnarly when using anything else than cmd.exe (eg the GitHub Bash Shell)
Once my pull request goes in, this issue should be resolved:
https://github.com/TomWij/meteor/pull/56