linkedin / linkedin/dustjs

dust-full js looks for ./parser ./dust js files inside dist folder

Open
#789 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
2.9k
Forks
461
PR merge metrics
No merged PRs in 30d

Description

Webpack throws error while bundling if i point dustjs-linkedin to nodemodules dustjs-linkedin/dist/dust-full.js
why does the dust-full js file looks for these files in the dist folder
./parser ./server ./dust js
is there anything that i am doing wrong here please let me know ....
![screenshot from 2018-12-19 16-41-17](https://user-images.githubusercontent.com/16647331/50216855-f3bcb680-03ac-11e9-9e31-338a4c038148.png)

![screenshot from 2018-12-19 16-36-16](https://user-images.githubusercontent.com/16647331/50216789-b9ebb000-03ac-11e9-8b44-285844bc8935.png)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Webpack error while importing nodemodules dustjs-linkedin/dist/dust-full.js. Inspect dist/dust-full.js and the referenced ./parser, ./server, and ./dust paths to determine whether the package layout or module resolution causes the failure; done means the issue has a confirmed cause and a documented or tested resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, webpack
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.