-
Notifications
You must be signed in to change notification settings - Fork 35
precompile
files are not included in npm package
#250
Comments
This fixes #251 - tested on scoped npm module (@ndreckshage/tungstenjs) |
Would the template compiler APIs exposed here work? I use The published npm package is intentionally only the dist files to prevent deep-linking into the repo when consuming the library (also since including a non-compiled build would require consuming libraries to use the same versions of loaders like babel). Custom builds can be done by cloning the repo and installing its dev dependencies. If there's something we're not exposing that is necessary to consume tungsten then the best way to handle that would be to expose it on the tungsten API itself. And yes, I know all of this should be updated in our docs. I'm hoping to do a significant update of the readme soon. |
Perfect! I can submit a PR to update the docs if you'd like. |
That'd be awesome. I'm unable to do much until next week but I can spend some time on them then. |
Closing, looks like primary problem was addressed with #255. |
What I'm trying to do
Install the
tungstenjs
and use thetungsten_template
webpack loader from within thetungstenjs
installation, as outlined in the project's documentation.Expected result
Webpack is able to look up
tungsten_template
from thenode_modules/tungstenjs/precompile
directoryActual result
The
precompile
directory is not present in the installation's directory. Onlydist
is available below the top level.Steps to reproduce
Something that stands out in the installed
package.json
within tungsten's install directory is that thefiles
property looks likebut I can't seem to figure out what configuration is causing this. Please let me know if more information is needed!
The text was updated successfully, but these errors were encountered: