Local build not work

rstoenescu

@fsgiudice hi, does this help?

‘’‘js
npm install -g npm-windows-upgrade
npm-windows-upgrade
‘’’
Then erase node_modules and npm install again.

fsgiudice

Hi @rstoenescu
nope, same error.

Also updated to latest node 6.9.2 and npm 4.0.5 but same results.
npm run dev works correctly, instead npm run build not.
It seems to me as some other global is missing.
Thank you for your effort.

Francesco

rstoenescu

Are you experiencing this with Quasar’s repo or with an app?

fsgiudice

@rstoenescu,
actually with my fork of https://github.com/quasarframework/quasar.
To be sure, I have cloned your repository directly and, in a empty folder, I did:

git clone https://github.com/quasarframework/quasar.git
npm install
npm run dev

and it works, but if I do

npm run build

the error is exactly the same reported above.

Francesco

rstoenescu

@fsgiudice have you installed npm-windows-upgrade? I just tried building Quasar on Win 10 7 under cygwin:

IEUser@IE11Win7 ~/quasar-dev
$ npm run build

> quasar-framework@0.12.1 build C:\cygwin\home\IEUser\quasar-dev
> node build/script.build.js

 Cleaned build artifacts.

 Building...
dist/quasar.ios.styl 118.00kb
dist/quasar.ios.css 226.23kb
dist/quasar.mat.styl 120.56kb
dist/quasar.mat.css 247.62kb
dist/quasar.ios.standalone.css 279.33kb
dist/quasar.mat.standalone.css 300.64kb
dist/quasar.ios.standalone.min.css 220.42kb
dist/quasar.mat.standalone.min.css 239.52kb
dist/quasar.common.js 312.03kb
dist/quasar.es6.js 280.72kb
dist/quasar.standalone.js 312.38kb
dist/quasar.standalone.min.js 199.98kb
dist/quasar.standalone.min.js.map 538.39kb
dist/quasar.standalone.min.js.gz 44.10kb

IEUser@IE11Win7 ~/quasar-dev
$

IEUser@IE11Win7 ~/quasar-dev
$ npm -v
3.10.8

IEUser@IE11Win7 ~/quasar-dev
$ node -v
v6.9.1

IEUser@IE11Win7 ~/quasar-dev

edit: Wait, silly me. That’s Windows 7.

fsgiudice

@rstoenescu
Yes, already done months ago and again with your last request.
But I’m not under cygwin environment.
Tell me something about this, because it could be the difference.

s.molinari

https://www.cygwin.com/

Scott

fsgiudice

@s.molinari
Sorry for misunderstanding, I know what cygwin is, but what is relation with npm and node?
Is it a prerequisite of those?
Because I use gnuwin32 for some other things and probably it clashes.

s.molinari

I have no idea, but are you on a 32bit machine?

Scott

fsgiudice

@s.molinari
No, 64bit

s.molinari

Hmm…wouldn’t you want to use gnuwin64 then? Not sure that would make any difference, but it just might considering Node is working with 64 bits.

Scott

rstoenescu

Seems like Stylus breaks. It may be due to the @imports within Stylus files. @fsgiudice do you have some time to make some experiments?

Search *.styl files and change imports that start with ‘./’ by removing this string.
and second test:
Replace in all styl file imports ‘/’ to ‘’… maybe the path separator is an issue in Stylus on Windows10 ?

fsgiudice

@rstoenescu
Bingo!
changing to

@import 'src/themes/quasar.core.variables'

@import 'src/components/*/*.mat'
@import 'src/css-components/*/*.mat'
@import 'src/vue-components/*/*.mat'

@import 'src/themes/quasar.core.definitions'

and other files

        modified:   build/script.build.stylus.js
        modified:   src/themes/quasar.core.definitions.styl
        modified:   src/themes/quasar.core.variables.styl
        modified:   src/themes/quasar.ios.styl
        modified:   src/themes/quasar.mat.styl

now npm run build works.
But now I get error on npm run dev
So it is definitively a path problem on build script files.
I’m checking if I can find the error.

Francesco

fsgiudice

Update:
no result playing with paths. As written before latter case works in build mode, former in dev mode.

rstoenescu

@fsgiudice Will see what I can do. Won’t be able to take care of this too soon though. Simply ignore the build step if you are writing code for Quasar. Just “npm run dev” and add pages to the ‘/dev’ that use the features you are working on.

fsgiudice

@rstoenescu
Hi, I already did so.
But with build I can use my fork like quasar-edge in package.json in my test apps.
The other way I tried was to add new components directly to my project, but there were collisions with some paths.
Now I will try using quasar-edge and adding components to apps.
I hope I was clear.
Anyway thank you for your time.
Francesco

rstoenescu

@fsgiudice if you write components for Quasar you already have a playground app working there (/dev folder, which is run on npm run dev and compiles Quasar on the fly). Add a page for each new component and test it out there. No need to compile and then use in another repo.

No More Posting New Topics!

Local build not work