windows 10 pro office 2019 pro office 365 pro windows 10 home windows 10 enterprise office 2019 home and business office 2016 pro windows 10 education visio 2019 microsoft project 2019 microsoft project 2016 visio professional 2016 windows server 2012 windows server 2016 windows server 2019 Betriebssysteme office software windows server instagram takipçi instagram beğeni instagram görüntüleme instagram otomatik beğeni facebook beğeni facebook sayfa beğenisi facebook takipçi twitter takipçi twitter beğeni twitter retweet youtube izlenme youtube abone instagram

How to use rollup with sirv for a svelte app

Asked By: Anonymous

unfortunately, I was not able to find anything in the rollup documentation. I am building a website with Svelte and rollup and need different environment variables for production, testing and development.

This is my scripts section of my package.json:

  "scripts": {
    "build": "cross-env rollup -c",
    "autobuild": "BACKEND_SSL=true SERVER_PORT=443 rollup -c -w",
    "devbuild": "rollup --environment BACKEND_SSL:false,SERVER_NAME:localhost,SERVER_PORT:4000 -c -w",
    "testbuild": "BACKEND_SSL=false SERVER_NAME=localhost SERVER_PORT=4000 rollup -c",
    "dev": " run-p start:dev",
    "start": "sirv public --single",
    "start:dev": "cross-env --max-old-space-size=16000 sirv public --single --dev --cors",

I can’t figure out how to use the start:dev command with one of the autobuild or testbuild commands. Somehow the environment variables are always the one from the devbuild script, even when I remove all the scripts. Are these variables also specified somewhere else? I tried this:

"start:dev": "cross-env --max-old-space-size=16000 sirv public --single --dev --cors autobuild"

and this:

"start:dev": "cross-env --max-old-space-size=16000 sirv public --single --dev --cors BACKEND_SSL=true SERVER_PORT=443 rollup -c -w"

but nothing seems to work. What do I not see here? Is there maybe some actual documentation on sirv? I could only scrap by some information via the -h flag.


Answered By: Anonymous

Okay, I figured it out. sirv is only a static fileserver, so it has nothing to do with my problem. The solution lies in the run-p command. This is short for npm run all. So I have to do this in my dev script:

"dev": " run-p autobuild start:dev"

So first rollup runs and builds and watches the files and then sirv runs and delievers the compiled files. To be honest, what dumbfounds me most, is that it worked before, where only the start:dev command was executed.

techinplanet staff

Windows 10 Kaufen Windows 10 Pro Office 2019 Kaufen Office 365 Lizenz Windows 10 Home Lizenz Office 2019 Home Business Kaufen windows office 365 satın al follower kaufen instagram follower kaufen porno
Alanya escort Manavgat escort Fethiye escort Kemer escort Didim escort Gaziantep escort Denizli escort Adana escort Hatay escort Aydın escort İzmir escort Ankara escort Antalya escort Bursa escort İstanbul escort Kocaeli escort Konya escort Muğla escort Malatya escort Kayseri escort Mersin escort Samsun escort Sinop escort Tekirdağ escort Eskişehir escort Yalova escort Rize escort Amasya escort Balıkesir escort Çanakkale escort Bolu escort Erzincan escort Şırnak escort Van escort Yozgat escort Zonguldak escort Afyon escort Adıyaman escort Bilecik escort Aksaray escort Ağri escort Bitlis escort Siirt escort Çorum escort Burdur escort Diyarbakir escort Edirne escort Düzce escort Erzurum escort Kırklareli escort Giresun escort Kilis escort Kars escort Karabük escort Kırıkkale escort Mardin escort Kırşehir escort Maraş escort Manisa escort Muş escort Kastamonu escort Ordu escort Nevşehir escort Sakarya escort Osmaniye escort Şanliurfa escort Sivas escort Trabzon escort Tokat escort Ardahan escort Bartın escort Karaman escort Batman escort Bayburt escort Bingöl escort Elaziğ escort Gümüşhane escort Hakkari escort Isparta escort Uşak escort Igdır escort