16 Matching Annotations
  1. Nov 2020
    1. Everyone working in a TypeScript project that grows beyond a certains limit will eventually experience the situation commonly described as path hell, the snippet below is an example of such hell.
    1. Unlike some other languages, Sass doesn’t require that you use ./ for relative imports. Relative imports are always available.
    1. The sass-loader uses Sass's custom importer feature to pass all queries to the Webpack resolving engine. Thus you can import your Sass modules from node_modules. Just prepend them with a ~ to tell Webpack that this is not a relative import: @import '~bootstrap';
  2. Oct 2020
    1. The react community has become a big cargo cult. There are some good ideas in the community and many Bad Ideas™. Paving the bad idea cowpaths lends a sense of legitimacy to these bad technical ideas that is not merited.
    2. I agree that "it feels gross" is a bad reason. "not paving a bad cowpath" is a much better reason.
    3. If the react cargo cult didn't have the JSX cowpath paved for them and acclimated to describing their app interface with vanilla javascript, they'd cargo cult around that. It's really about the path of least resistance and familiarity.
  3. Nov 2019
    1. To make this even easier, you can also simply import @testing-library/react/dont-cleanup-after-each which will do the same thing.
  4. May 2017
    1. var webpack = require('webpack');

      Note you should also add:

      const path = require('path'); 

      See following comments for rationale.

    2. path: 'dist'

      Again, this will throw errors. The solution utilises 'path' (see comment above). The code should look like this in new versions of webpack:

      path: path.resolve(__dirname, 'dist')
  5. Jul 2015
    1. Many subjects and ideas link together Leveling-up in one area can mean also leveling-up in another You don’t have to learn everything about a subject The learner (with some prompting) can decide the learning goal It’s OK to jump around a bit while learning