Hide source code when creating component library

[mrados7]

Hello 👋 .
Is it possible to hide source code of components when building component library.
Currently when I build component library using bob my source code is shown in node_modules when installed.
Is it possible to hide src/ directory in build or at least obfuscate code?

[satya164]

Just remove src from files, react-native entry, and disable sourceMaps

[mrados7]

Hey @satya164, thanks for reply. Already tried that but still gives me src/ directory in final (published) package. But when I do build (yarn prepare) it doesn't show src/ directory there. I new to this so I'm most likely doing some dumb mistake, just can't figure out.

• tsConfig.json:

  "compilerOptions": {
    "allowUnreachableCode": false,
    "allowUnusedLabels": false,
    "esModuleInterop": true,
    "importsNotUsedAsValues": "error",
    "forceConsistentCasingInFileNames": true,
    "jsx": "react",
    "lib": ["esnext"],
    "module": "esnext",
    "moduleResolution": "node",
    "noFallthroughCasesInSwitch": true,
    "noImplicitReturns": true,
    "noImplicitUseStrict": false,
    "noStrictGenericChecks": false,
    "noUncheckedIndexedAccess": true,
    "noUnusedLocals": true,
    "noUnusedParameters": true,
    "resolveJsonModule": true,
    "skipLibCheck": true,
    "strict": true,
    "target": "esnext",
    "sourceMap": false
  }
}

• package.json:

  "main": "lib/commonjs/index",
  "module": "lib/module/index",
  "types": "lib/typescript/index.d.ts",
  "react-native": "src/index",
  "source": "src/index",
  "files": [
    "lib",
    "android",
    "ios",
    "cpp",
    "*.podspec",
    "!lib/typescript/example",
    "!ios/build",
    "!android/build",
    "!android/gradle",
    "!android/gradlew",
    "!android/gradlew.bat",
    "!android/local.properties",
    "!**/__tests__",
    "!**/__fixtures__",
    "!**/__mocks__",
    "!**/.*"
  ],
}

• build generates:
  

• after installation of published package to another project:
  

Basically all the directory structure is copied over. Package is published on github private repository -> https://npm.pkg.github.com/

[satya164]

compiler options are irrelevant. npm only cares about the files entry and .npmignore. you can check what gets published by running npm pack or npm pack --dry-run. after you remove src from files, it won't be included in the package which you can verify with the above commands.

what commands are you running to publish your package? that looks like your whole github repository which includes .github, example folders etc. which shouldn't be there in the published package.

though I'd also emphasize that unless you're obfuscating your code, there isn't really much hidden by not publishing src folder. your client-side libraries shouldn't include any secrets that you don't want others to be able to find. client-side code is always public. someone can still figure out stuff after obfuscating.

[mrados7]

Alright it was dumb mistake in the end. My github actions were using yarn publish which I think (correct me if wrong) doesn't care about "files" in package.json.
I don't include any secret or something like that, but it doesn't make sense to publish source code as well when not needed. Thank you so much for your help @satya164 !

[satya164]

Yarn should work too but it has some strange behavior so I recommend using npm for publishing anyway