Replies: 1 comment
-
| It's just the structure we've decided on. No big considerations here. It's the artifact of us also publishing CDN modules and we had planned to publish legacy packages and so on. We do not consider the folder structure of our packages as part of the public API. Depend on it at your own risk. You can write your own publish script that does whatever you want. The world is yours! | 
Beta Was this translation helpful? Give feedback.
                  
                    0 replies
                  
                
            
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
        
    
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
after run
npm run buildthe outputs is in 'build' directory,
npm publishit would push 'build' directory to the npm
How can I publish package to the private npm without the wrapped 'build' directory like the offical does?
Beta Was this translation helpful? Give feedback.
All reactions