You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 19, 2024. It is now read-only.
Output bundles contain complete file path information (including username - if project is in user director).
This also causes a regular error with the workers.js file:
VM126171:1 Access to XMLHttpRequest at 'file:///C:/Users/<username>/web/apps/datafi/node_modules/arcgis-js-api/core/workers/worker.js' from origin 'http://lvh.me:9000' has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-extension, https.
Expected Behavior
I don't believe that this should be happening. Its a potential security/privacy issue. File paths should be referenced via their node_module package.
What's happening here is webpack is splitting the code up into different bundles because the import('path'); is a dynamic import that may or not be used in this bundle.
The use case is my app can load the default esri/Map or it may conditionally load the esri/WebMap class in place and not need to load both. Same thing for esri/views/SceneView vs esri/views/MapView.
green3g
changed the title
Investigate issue with full file path names getting into output bundles
Full path file name to worker.js causing error in output bundle
Nov 8, 2018
Description
I'd like to open up a discussion on finding a solution to the question mentioned here:
https://stackoverflow.com/questions/51986624/webpack-babel-loader-outputting-full-c-drive-urls-in-bundles/52007420#52007420
Output bundles contain complete file path information (including username - if project is in user director).
This also causes a regular error with the workers.js file:
Expected Behavior
I don't believe that this should be happening. Its a potential security/privacy issue. File paths should be referenced via their node_module package.
Actual Behavior
File paths are getting included like this:
Possible Fix
First we should determine whether or not this is being caused by the dojo webpack/arcgis webpack plugin.
Steps to Reproduce
All builds seem to have this output.
Context
Its slightly disconcerting that my username gets put in public facing javascript files.
Your Environment
The text was updated successfully, but these errors were encountered: