Add packages with prefix vsf- to webpack process
See original GitHub issueWhat is the motivation for adding / enhancing this feature?
Currently none of the third party libs are processed through loaders in our webpack process. While it’s ok for most of them it’s not ok for 3rd party VS modules. They should he included into our webpack process.
This requires changing regular expressions for loader in core/build
folder.
What are the acceptance criteria
node_modules
with name starting fromvsf-
should be included into our webpack process for all loaders (as it would be in in thecore
)
Can you complete this feature request by yourself?
NO
Additional information
Feel free to ask for details on slack
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:20 (12 by maintainers)
Top Results From Across the Web
Add packages with prefix vsf- to webpack process · Issue #2271
I added my test npm package path to the babel loader rule include property. path.resolve(__dirname, '../../node_modules/vsf-layered-navigaton'),.
Read more >Package exports - webpack
The exports field in the package.json of a package allows to declare which module should be used when using module requests like import...
Read more >Module Methods - webpack
This section covers all methods available in code compiled with webpack. When using webpack to bundle your application, you can pick from a...
Read more >Configuration - webpack
$ npx webpack init [webpack-cli] For using this command you need to install: '@webpack-cli/generators' package. [webpack-cli] Would you like to install '@ ...
Read more >Output Management - webpack
However, a few plugins exist that will make this process much easier to manage. ... Let's add some logic to our src/print.js file:...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@zimme sorry this was caused by merge into master. I’m reopening it.
This issue has been closed due to inactivity.
If you want to re-open the issue, please re-create the issue, and post newer information on this problem.