Question Would you Accept a PR that changes Package Structures

[frank-dspeed]

I Would love when all package-name/package.json files would be valid that means

• main points to src/file not none existing dist
• for dist a extra package.json gets written on RELEASE inside dist only dist and needed files get published to npm while github src stays useable directly.
• Translate all name/name require calls to name/name.js so that it will be even load able via node resolve and other tooling?

[frank-dspeed]

The current package structure on github works like a copy protection :) i know what i am talking about i was many years active in the warez scene :) as i was young your Package Structure at present beats the most copy protections of modern games :)

[justinbmeyer]

To make this change, we’d need to change how canjs/canjs works. We run integration tests that currently depend on packages including test files. We’d need to change canjs/canjs to install using tagged hit releases instead.

[frank-dspeed]

@justinbmeyer i can refactor that tests to use the github repos that will offer tests as usal its only a change to drop steal my main goal is to get all that build and loaded without steal in es6 at present i have code mods for that and a rollup plugin that don't uses package json to resolve canjs packages.

i could resolve canjs packages then also via github src npm install canjs/can-type will use github the package.json will point to src all will work the tests are there everything is there.

we could even let the package.json inside of the repo reference other github packages canjs/can-name and the dist/package.json will use the package name without canjs/ this will work really well and will fix a lot of my problems

[frank-dspeed]

and i would love 2 fix at last 2 packages file naming

              //special case by can-define-lazy-value
              `${PackagePath}${file}/${file.split('can-')[1]}.js`, 
              //special can observeable mixin
              `${PackagePath}${file}/src/mixins.js`,

and maybe if you allow i would love to apply the naming convetion can-package/can-package.js or can-package/src/can-package.js to all repos some reference index.js

[frank-dspeed]

this is my current can- indipendent resolve algorythm :D for your require statments

          const tryResolv = file => {
            return [
              `${PackagePath}${file}.js`, //=> packages/file.js most time wrong right if can-assign/map/map
              `${PackagePath}${file}/${file}.js`, //=> right if can-assign packages/can-assign/can-assign.js
              `${PackagePath}${file}/src/${file}.js`, //=> right if can-assign packages/can-assign/can-assign.js
              `${PackagePath}${file}/index.js`, //=> right if can-assign packages/can-assign/index.js
              `${PackagePath}${file}/src/index.js`, //=> right if can-assign packages/can-assign/index.js
              //special case by can-define-lazy-value
              `${PackagePath}${file}/${file.split('can-')[1]}.js`, 
              //special can observeable mixin
              `${PackagePath}${file}/src/mixins.js`,
            ]
          }

[frank-dspeed]

by the way i got qunit working without steal with my ES6 code the qunit tests all pass and run blazing fast