dr-dimitru on master
📔 Documentation update (compare)
dr-dimitru on 1.3.0
dr-dimitru on master
Add prompt before data removal … Minor codebase enhancements 📦 1.3.0 __Changes:__ - 🔧 Fi… (compare)
This is the error I get on windows: `Generating the index.html...
fs.js:772
return binding.unlink(pathModule._makeLong(path));
^
Error: EPERM, operation not permitted 'C:\Users\garethw\Desktop\Tidy\rmsClient\b
undle\main.js'
at Object.fs.unlinkSync (fs.js:772:18)
at C:\Users\garethw\AppData\Roaming\npm\node_modules\meteor-build-client\met
eor.js:45:20
at Array.forEach (native)
at deleteFolderRecursive (C:\Users\garethw\AppData\Roaming\npm\node_modules\
meteor-build-client\meteor.js:40:15)
at Object.module.exports.cleanUp (C:\Users\garethw\AppData\Roaming\npm\node_
modules\meteor-build-client\meteor.js:165:9)
at C:\Users\garethw\AppData\Roaming\npm\node_modules\meteor-build-client\mai
n.js:84:20
at null._onTimeout (C:\Users\garethw\AppData\Roaming\npm\node_modules\meteor
-build-client\queue.js:41:11)
at Timer.listOnTimeout [as ontimeout] (timers.js:112:15)
`
Yup done that. Same thing. I'm pretty sure this is linked to the file name issue I posted. The css and js file names cannot be served by http-server because the filenames are too long. I have to shorten them, after which they work fine. ```Generating the index.html...
fs.js:772
return binding.unlink(pathModule._makeLong(path));
^
Error: EPERM, operation not permitted 'C:\rms5Client\5bfc97ade90aff3c0e92c06cc55
823f48b82e302.css'
at Object.fs.unlinkSync (fs.js:772:18)
at Object.module.exports.addIndexFile (C:\Users\garethw\AppData\Roaming\npm\
node_modules\meteor-build-client\meteor.js:118:16)
at C:\Users\garethw\AppData\Roaming\npm\node_modules\meteor-build-client\mai
n.js:79:20
at null._onTimeout (C:\Users\garethw\AppData\Roaming\npm\node_modules\meteor
-build-client\queue.js:41:11)
at Timer.listOnTimeout [as ontimeout] (timers.js:112:15)
```
why should the file names length be a problem, when they work on any meteor server?
googling the EPERM issue i found this:
"Oh my god. That is it after all. I disabled my anti-virus software (NOD32 in my case) and retried the original code. It installed flawlessly on the first go. That is just, wow."
npm cache clean
Generating the index.html...
fs.js:772
return binding.unlink(pathModule._makeLong(path));
^
Error: EPERM, operation not permitted 'C:\Users\garethw\Desktop\Tidy\rmsClient\5
bfc97ade90aff3c0e92c06cc55823f48b82e302.css'
at Object.fs.unlinkSync (fs.js:772:18)
at Object.module.exports.addIndexFile (C:\Users\garethw\AppData\Roaming\npm\
node_modules\meteor-build-client\meteor.js:120:16)
at C:\Users\garethw\AppData\Roaming\npm\node_modules\meteor-build-client\mai
n.js:84:20
at null._onTimeout (C:\Users\garethw\AppData\Roaming\npm\node_modules\meteor
-build-client\queue.js:41:11)
at Timer.listOnTimeout [as ontimeout] (timers.js:112:15)
Hi guys. Is there a step I'm missing when using this and Iron Router? I can hit the login page of my app and get redirected based on the logic in a Router.onBeforeAction
call but then navigating anywhere else just gives me a blank page.
I'm building like this meteor-build-client ../build -u http://localhost:8081
and then accessing the app from a Python SimpleHTTPServer.
meteor-build-client ../tmp -p /casa/
. After I copy all files to /var/www/html/casa
folder. I expected to see my website displayed, but I found http://linux.pentlab.com/sockjs/info?cb=_hp4ljvczb 404 (Not Found)
. Although the index.html
file appears Meteor.disconnect ()
the browser does not display the content.