Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Oleksiy Golovko
    @zindel
    renaming is an issue yet
    Rauan Mayemir
    @rauanmayemir
    what kind of cache is this? how do i 'reset' it?
    Oleksiy Golovko
    @zindel
    you can fix it by removing the cache rm -rf node_modules/.cache/fpack
    Rauan Mayemir
    @rauanmayemir
    👌worked like a charm
    Oleksiy Golovko
    @zindel
    or there is a --no-cache flag
    Rauan Mayemir
    @rauanmayemir
    i have a suspicion cache is not being set properly
    image.png
    Oleksiy Golovko
    @zindel
    why?
    Rauan Mayemir
    @rauanmayemir
    wait, forgot the first image
    image.png
    it used to show me Cache: no on initial run
    or is it about being a cold start?
    Oleksiy Golovko
    @zindel
    yep
    it means that cache file was not loaded
    Rauan Mayemir
    @rauanmayemir
    ok, now i see
    Oleksiy Golovko
    @zindel
    I think we need the better wording here
    Rauan Mayemir
    @rauanmayemir
    yeah, i think so
    Oleksiy Golovko
    @zindel
    @rauanmayemir what would be the clearer message for you?
    Rauan Mayemir
    @rauanmayemir
    i think something like 'Cache: empty'/ 'Cache: yes'/'Cache: disabled' would make it more helpful
    Oleksiy Golovko
    @zindel
    @rauanmayemir just committed the fix for renamings & deletions in watch mode
    Rauan Mayemir
    @rauanmayemir
    👍
    Rauan Mayemir
    @rauanmayemir
    @zindel hey! have you guys considered adding built-in SASS support? as in native-native sass/scss compiler
    Rauan Mayemir
    @rauanmayemir
    i wonder what would one need to do had he wanted to add such support
    or try and play around
    Rauan Mayemir
    @rauanmayemir
    though i'd rather start with something easier, like file-loader or image-loader
    Oleksiy Golovko
    @zindel
    Hi @rauanmayemir!
    we haven't thought enough how to do it in a native way yet
    Although we're trying to maintain the compatibility with webpack loaders
    see this issue: fastpack/fastpack#41
    Rauan Mayemir
    @rauanmayemir
    i didn't quite understand the issue. does that mean file-loader is baked-in or you just plug the webpack's file-loader in-process?
    Oleksiy Golovko
    @zindel
    sass-loader specifically is not tested yet, but we have a plan to test it before the release
    not really
    Rauan Mayemir
    @rauanmayemir
    i meant trying to replace all the loaders with native built-in modules, at least for basic ones
    Oleksiy Golovko
    @zindel
    if we see such loaders in the config - we start the node process as the service
    and communicate the config right to it, feeding the result back to the main process
    it is absolutely on the target system to have the needed dependencies installed, as well as 'loader-runner'
    we have couple integration tests built-in, to demonstrate the example config
    for instance, see this one:
    https://github.com/fastpack/fastpack/tree/master/test/pack-cra
    and specifically, this file: https://github.com/fastpack/fastpack/blob/master/test/pack-cra/pack-cra.test.js
    Rauan Mayemir
    @rauanmayemir
    have you considered e.g replacing the node process part with native call? 'just because'
    Oleksiy Golovko
    @zindel
    we did :)
    although we don't have enough resources
    yesterday I dreamed about the OCaml native CSS parser
    :)
    Rauan Mayemir
    @rauanmayemir
    if you can give some guidance, i'd love to start with the basic loaders and try contributing
    Oleksiy Golovko
    @zindel
    if you want to try it out I can walk you through the architecture
    great!
    would it be easier with some sort of voice chat / screen sharing?
    Rauan Mayemir
    @rauanmayemir
    sure