packages/build-tools/tasks/task-collections.js
async function getExtraTasks() {
  config = config || (await getConfig());

  switch (config.env) {
    case 'pl':
      extraTasks.patternLab = require('./pattern-lab-tasks');
      break;
    case 'static':
      extraTasks.static = require('./static-tasks');
      break;
    case 'pwa':
      delete require.cache[require.resolve('./api-tasks')];
      extraTasks.api = require('./api-tasks');
      extraTasks.patternLab = require('./pattern-lab-tasks');
      extraTasks.static = require('./static-tasks');
      break;
  }

  if (config.wwwDir) {
    extraTasks.server = require('./server-tasks');
  }

  return extraTasks;
}
async function getExtraTasks() {
  config = config || (await getConfig());

  switch (config.env) {
    case 'pl':
      extraTasks.patternLab = require('./pattern-lab-tasks');
      break;
    case 'static':
      extraTasks.static = require('./static-tasks');
      break;
    case 'pwa':
      delete require.cache[require.resolve('./api-tasks')];
      extraTasks.api = require('./api-tasks');
      extraTasks.patternLab = require('./pattern-lab-tasks');
      extraTasks.static = require('./static-tasks');
      break;
  }

  if (config.wwwDir) {
    extraTasks.server = require('./server-tasks');
  }

  return extraTasks;
}
async function getExtraTasks ( ) { config = config || ( await getConfig ( ) ) ; switch ( config . env ) { case 'pl' : extraTasks . patternLab = require ( './pattern-lab-tasks' ) ; break ; case 'static' : extraTasks . static = require ( './static-tasks' ) ; break ; case 'pwa' : delete require . cache [ require . resolve ( './api-tasks' ) ] ; extraTasks . api = require ( './api-tasks' ) ; extraTasks . patternLab = require ( './pattern-lab-tasks' ) ; extraTasks . static = require ( './static-tasks' ) ; break ; } if ( config . wwwDir ) { extraTasks . server = require ( './server-tasks' ) ; } return extraTasks ; }
These tasks are present based on optional conditions like `config.env` and should only be `require`-ed when it's the right env due to each file's setup where it tries to grab specific files - and of course the tasks should only run in the correct `env` as well.
These tasks are present based on optional conditions like config . env and should only be require - ed when it s the right env due to each file s setup where it tries to grab specific files - and of course the tasks should only run in the correct env as well .