serialize-javascript
is being used, I don't think there's any vulnerability. I think that issue is for websites that use it and deal with 3rd party code inside their application. In the case of jspm and terser plugin, it's just taking your code and compiling it, and you will already give jspm and terser both full access to all code to manipulate it any way those tools see fit (including access to run any and all of that code) so it doesn't matter much. In this case, there is trust in jspm and terser.
@guybedford Does jspm CDN support semver? I tried https://dev.jspm.io/@here/harp-omv-datasource@^0.13.0/index-worker but that doesn't work.
It'd be great if semver syntax was supported, just like with unpkg
.
node --max-old-space-size=2048 node_modules/jspm/jspm bundle-sfx main public/myapp.js --inject --minify --source-map-contents && mv public/myapp* dist/public && cp public/config.js dist/public && jspm unbundle
failed with exit code 137node --max-old-space-size=8192 node_modules/jspm/jspm bundle-sfx main public/myapp.js --inject --minify --source-map-contents
failed with exit code 137--inject
? Looking back at these docs I'm thinking you may be able to simplify the command a bit to narrow in on the issue: https://jspm.org/docs/0.16/production-workflows.html
SyntaxError: Unexpected token {
at new Function (<anonymous>)
at dew (file:///home/vika/Projects/blogblaze/jspm_packages/npm/uglify-js@2.8.29/tools/node.dew.js:46:3)
at dew (file:///home/vika/Projects/blogblaze/jspm_packages/npm/pug-filters@3.1.1/lib/run-filter.dew.js:38:16)
at dew (file:///home/vika/Projects/blogblaze/jspm_packages/npm/pug-filters@3.1.1/index.dew.js:8:23)
at dew (file:///home/vika/Projects/blogblaze/jspm_packages/npm/pug@2.0.4/lib/index.dew.js:40:17)
at file:///home/vika/Projects/blogblaze/jspm_packages/npm/pug@2.0.4/lib/index.js:2:16
at ModuleJob.run (internal/modules/esm/module_job.js:95:12)
when using globally-installed jspm 2.0.0-beta7 and trying to use pug via jspm install pug
and subsequent import
:point_up: March 27, 2020 5:40 PM
3.0 is a new reframing of the concept, will aim to provide more info soon
i wonder how soon it'll be :3
Hi, one of our legacy projects on 0.16.53 has randomly started failing to build. It fails to authenticate with github on all of the projects:
warn Error on download for github:lorenzofox3/Smart-Table
Unauthorized response for GitHub API.
Use jspm registry config github to reconfigure the credentials, or update them in your ~/.netrc file.
err Error downloading github:lorenzofox3/Smart-Table.
Using curl to the github api with -u user:token
seems to be successful, and so does reconfiguring:
Enter your GitHub username:DulithaRanatunga
Enter your GitHub password or access token:redacted
Would you like to test these credentials? [yes]:
ok GitHub authentication is working successfully.
ok Registry github configured successfully.
But i'm unable to progress past the above error ^.
I'm unsure why it started to fail in the past week, and I'm wondering if others have experienced this?
(Not providing auth credentials does hit the github rate limit issue :()