Giter Club home page Giter Club logo

ribcage-preview's People

Contributors

cscheye avatar joeybaker avatar mde avatar techwraith avatar

Stargazers

avatar

Watchers

avatar avatar avatar

Forkers

joeybaker cscheye mde

ribcage-preview's Issues

fragmentedOperation error

Error stacktrace:

~/repos/getable/OrdEx (master) ☢ ribcage preview components/list-cell-supplier-location/
[atomify] Proxying: http://localhost:4000
[atomify] Access URLs:
 ------------------------------------------
       Local: http://localhost:4001/default
    External: http://10.0.1.21:4001/default
 ------------------------------------------
          UI: http://localhost:3001
 UI External: http://10.0.1.21:3001
 ------------------------------------------
[atomify] Watching files...
[atomify] Bundle updated in 3223ms
File written to ../../../../../usr/local/lib/node_modules/ribcage/node_modules/ribcage-preview/node_modules/atomify/lib/_bundle.js

/usr/local/lib/node_modules/ribcage/node_modules/ribcage-preview/node_modules/atomify/node_modules/browser-sync/node_modules/socket.io/node_modules/engine.io/node_modules/ws/lib/Receiver.js:222
  if (!this.state.fragmentedOperation) this.unfragmentedBufferPool.reset(true)
                 ^
TypeError: Cannot read property 'fragmentedOperation' of null
    at Receiver.endPacket (/usr/local/lib/node_modules/ribcage/node_modules/ribcage-preview/node_modules/atomify/node_modules/browser-sync/node_modules/socket.io/node_modules/engine.io/node_modules/ws/lib/Receiver.js:222:18)
    at Receiver.opcodes.1.finish (/usr/local/lib/node_modules/ribcage/node_modules/ribcage-preview/node_modules/atomify/node_modules/browser-sync/node_modules/socket.io/node_modules/engine.io/node_modules/ws/lib/Receiver.js:394:12)
    at Receiver.<anonymous> (/usr/local/lib/node_modules/ribcage/node_modules/ribcage-preview/node_modules/atomify/node_modules/browser-sync/node_modules/socket.io/node_modules/engine.io/node_modules/ws/lib/Receiver.js:372:33)
    at Receiver.add (/usr/local/lib/node_modules/ribcage/node_modules/ribcage-preview/node_modules/atomify/node_modules/browser-sync/node_modules/socket.io/node_modules/engine.io/node_modules/ws/lib/Receiver.js:87:24)
    at Socket.firstHandler (/usr/local/lib/node_modules/ribcage/node_modules/ribcage-preview/node_modules/atomify/node_modules/browser-sync/node_modules/socket.io/node_modules/engine.io/node_modules/ws/lib/WebSocket.js:718:22)
    at Socket.emit (events.js:95:17)
    at Socket.<anonymous> (_stream_readable.js:764:14)
    at Socket.emit (events.js:92:17)
    at emitReadable_ (_stream_readable.js:426:10)
    at emitReadable (_stream_readable.js:422:5)

startup speed

It's really slow, but I'm not sure there's a lot we can do. Basic benchmarks:

load server deps: 1858ms
load cli deps: 1862ms
stat validation checks: 1ms
find paths: 0ms
boot: 3014ms

It's the require calls that are taking the time :(

Crashing on file save

2e58479#diff-168726dbe96b3ce427e7fedce31bb0bcR9 causes an uncaught error for me when saving example/entry.css


Live reload server listening on port 4001
Atomify server listening on port 4000

File written to ../../../../usr/local/lib/node_modules/ribcage/node_modules/ribcage-preview/node_modules/atomify/lib/_bundle.js

child_process.js:945
    throw errnoException(process._errno, 'spawn');
          ^
Error: spawn EMFILE
    at errnoException (child_process.js:998:11)
    at ChildProcess.spawn (child_process.js:945:11)
    at Object.exports.spawn (child_process.js:733:9)
    at Static.gzip (/usr/local/lib/node_modules/ribcage/node_modules/ribcage-preview/node_modules/atomify/node_modules/browser-sync/node_modules/socket.io/lib/static.js:167:17)
    at ready (/usr/local/lib/node_modules/ribcage/node_modules/ribcage-preview/node_modules/atomify/node_modules/browser-sync/node_modules/socket.io/lib/static.js:370:14)
    at /usr/local/lib/node_modules/ribcage/node_modules/ribcage-preview/node_modules/atomify/node_modules/browser-sync/node_modules/socket.io/lib/static.js:103:9
    at /usr/local/lib/node_modules/ribcage/node_modules/ribcage-preview/node_modules/atomify/node_modules/browser-sync/node_modules/socket.io/node_modules/socket.io-client/bin/builder.js:219:7
    at fs.js:266:14
    at /usr/local/lib/node_modules/ribcage/node_modules/ribcage-gen/node_modules/hbs-dir/node_modules/vinyl-fs/node_modules/graceful-fs/graceful-fs.js:104:5
    at Object.oncomplete (fs.js:107:15)
Program ribcage preview components/input-field exited with code 8

flag for viewport

It would be super handy to have a flag to append <meta name="viewport" content="width=device-width, initial-scale=1.0"> to the head of the rendered HTML.

Files aren't getting compiled

Looks like the example files need to be named entry.*. Even after naming as such, I don't see a bundle.* created?

Continue to serve client side js even if it fails on the server

If there is an error in the component, it halts on the server, which prevents the use of client-side debugging tools. Ideally, an error should be logged out on the server, and the preview should still be delivered to the client, where debugging can be performed.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.