Proposal: ability include folder from node_modules to build pipeline

[Akiyamka]

In our apps we use our package registry under name space (@private-packges for example).
The difference between these packages and the regular npm packages that they are shipped as source code (.ts, .tsx, .module.css)

Unfortunately I don't see how I can include this directory in the build process.
The use of a workaround in the form of pre-build solve problem with ts and tsx, but I still can't solve problem with css modules

[404] /_dist_/@k2-packages/default-theme/variables.css.proxy.js

All this is similar to what I'm trying to replicate built-in functionality of the snowpack, rather than to ask him to come in another directory which is outside of src

Maybe we should add this setting to snowpack, what do you think?
I think this could look like setting include:

{
  "extends": "@snowpack/app-scripts-react",
  "include": ["src/**/*", "node_modules/@private-packges/**/*"],
}

[Akiyamka]

Unfortunately, even a workaround in the form of inversion exclude with glob !(pattern|pattern|pattern) does not help because of this
https://github.com/pikapkg/snowpack/blob/17e93b622e031d14ed7289818a73ed2d3273e669/packages/snowpack/src/config.ts#L27

[FredKSchott]

Yea, that line is probably preventing you here. Unfortunately we have a pretty strict rule that packages are packages, and not source code. But, there are two workarounds/loop holes for you:

• If you use npm link, we follow symlinked packages that point to directories outside of the node_modules directory, and will even watch them for changes.
• If you need to process unexpected code in packages, you can add installOptions.rollup.plugins in your config file to add custom rollup plugins to the Snowpack installer to handle TS, SASS, etc inside of packages.

[Akiyamka]

Thanks for the answer!