question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Haul creating random folders in each run in project root

See original GitHub issue

Current Behavior

Haul is pacakging the bundle and is being successfully loaded in both iOS and Android. There is no issue with the build, but haul is creating random folders in project root, prefixed as haul-start- while running Haul via yarn haul start command.

Please refer the screenshot: image

Expected Behavior

Haul should not be creating random folders each time it is being called, which would pollute the project root. If those folders are unavoidable either create single folder each time the command is run, which can then be added to .gitignore or provide option to the user to provide a path like /dist or /build to which these folders can be diverted.

Haul Configuration (webpack.haul.js)

import { createWebpackConfig } from "haul";
import path from "path";

export default {
  webpack: (env, defaults) => {
    const config = createWebpackConfig({
      // ...defaults,
      entry: `./index.js`,
      resolve: {
        // ...defaults.resolve,
        alias: {
          // ...defaults.resolve.alias,
          react: path.join(__dirname, "node_modules/react"),
          "react-native": path.join(__dirname, "node_modules/react-native")
        }
      }
    })(env);

    config.module.rules = [
      {
        test: /\.tsx?$/,
        loader: "ts-loader"
      },
      ...config.module.rules
    ];

    config.resolve.extensions = [
      ".js",
      ".ts",
      ".tsx",
      `.${env.platform}.ts`,
      ".native.ts",
      `.${env.platform}.tsx`,
      ".native.tsx",
      ...config.resolve.extensions
    ];

    return config;
  }
};

Your Environment

software version
Haul ^1.0.0-rc.13
react-native 0.58.4
node v11.6.0
npm or yarn 1.13.0

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:1
  • Comments:12 (10 by maintainers)

github_iconTop GitHub Comments

1reaction
thymikeecommented, Feb 17, 2019

Btw by default the asset destination is set to os tmp directory

0reactions
thymikeecommented, Mar 28, 2019

As confirmed with @sirajulm this is published under next tag (it points to 1.0.0-rc.15 now).

Read more comments on GitHub >

github_iconTop Results From Across the Web

PhpStorm - Configuring folders within a content root - JetBrains
In the Project tool window, by using the context menu of a folder. Mark directories under the content root. In the ...
Read more >
Directory Structure | Unreal Engine 4.27 Documentation
The Engine directory contains the engine itself and all of the tools that come with it. Each game folder contains all of the...
Read more >
Why does npm install a bunch of .cmd files on my project root ...
This happened to me - the fix on Windows was to go to c:\Users\{username}\.npmrc and remove the prefix.
Read more >
poppin folders
This opens up the Folder Size window, which shows you the size of each folder. Random empty folder keeps appearing on desktop. Your...
Read more >
Linux Root Folders Explained | Average Linux User
Linux Root Folders Explained. 15 Nov 2018. All Linux Root Folder. In this post, you will finally get the Linux root folders explained....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found